Triple
T6066805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helios 1 |
E135179
|
entity |
| Predicate | closestApproachToSun |
P20360
|
FINISHED |
| Object | inside Mercury’s orbit |
—
|
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: inside Mercury’s orbit | Statement: [Helios 1, closestApproachToSun, inside Mercury’s orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestApproachToSun Context triple: [Helios 1, closestApproachToSun, inside Mercury’s orbit]
-
A.
closestApproachDistance
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
B.
perihelionDistance
chosen
Indicates the shortest distance between an orbiting body and the Sun along its orbital path.
-
C.
hasAphelionNear
Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
-
D.
approximateDistanceFromSun
Indicates an estimated or rough measure of how far an entity is from the Sun, rather than an exact distance.
-
E.
perihelionDate
Indicates the date on which an orbiting body reaches its closest point to the Sun in 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0573f17088190a728f1c290cc9d1d |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.