Triple
T5561477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SDC |
E145774
|
entity |
| Predicate | trajectoryCoverage |
P64493
|
FINISHED |
| Object | inner solar system to Kuiper Belt |
—
|
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: inner solar system to Kuiper Belt | Statement: [SDC, trajectoryCoverage, inner solar system to Kuiper Belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trajectoryCoverage Context triple: [SDC, trajectoryCoverage, inner solar system to Kuiper Belt]
-
A.
trajectoryType
Indicates the kind or pattern of motion an entity follows along its path over time.
-
B.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
C.
movementComponentsCovered
Indicates that the movement or motion of an entity is fully accounted for or represented by a specified set of component movements.
-
D.
trajectoryExpansion
Indicates how the path or course of something spreads, widens, or diversifies over time or space.
-
E.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
- F. None of above. chosen
Provenance (4 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02019c6748190aeefb86f489f726a |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:36 p.m.