Triple
T18458239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 28978 Ixion |
E450959
|
entity |
| Predicate | locatedInEpoch |
P21934
|
FINISHED |
| Object | J2000 ecliptic |
—
|
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: J2000 ecliptic | Statement: [28978 Ixion, locatedInEpoch, J2000 ecliptic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInEpoch Context triple: [28978 Ixion, locatedInEpoch, J2000 ecliptic]
-
A.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
B.
locatedAtTime
Indicates that a location relationship holds during a specific time or time interval.
-
C.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
-
D.
epochReference
chosen
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
E.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.