Triple
T4780880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | outer Solar System |
E106160
|
entity |
| Predicate | approximateInnerBoundary |
P20346
|
FINISHED |
| Object | just beyond orbit of Neptune |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: just beyond orbit of Neptune | Statement: [outer Solar System, approximateInnerBoundary, just beyond orbit of Neptune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateInnerBoundary Context triple: [outer Solar System, approximateInnerBoundary, just beyond orbit of Neptune]
-
A.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
B.
nearBorderBetween
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
-
C.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
D.
hasUncertainBoundary
chosen
Indicates that the boundary or extent of something is not clearly defined, fixed, or precisely known.
-
E.
innerBoundaryDistanceFromSun
Indicates the distance from the Sun to the inner boundary of a specified region or zone.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.