Triple
T36613898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1943 Anteros |
E903547
|
entity |
| Predicate | perihelionIsInsideEarthOrbit |
P52316
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1943 Anteros, perihelionIsInsideEarthOrbit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perihelionIsInsideEarthOrbit Context triple: [1943 Anteros, perihelionIsInsideEarthOrbit, true]
-
A.
perihelionInsideOrbitOf
chosen
Indicates that the perihelion (closest point to the Sun) of one object's orbit lies within the orbital path of another object.
-
B.
hasPerihelionInside
Indicates that an object's closest point to the Sun (its perihelion) lies within the boundary or interior of another specified region or orbit.
-
C.
perihelionOutsideOrbitOf
Indicates that the closest point of one object's orbit to the Sun (its perihelion) lies outside the orbital path of another object.
-
D.
perihelionLocation
Indicates the location in space where an orbiting body is at its closest point to the Sun (its perihelion).
-
E.
perihelionDistance
Indicates the shortest distance between an orbiting body and the Sun along its orbital path.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.