Triple
T8577504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comet 67P/Churyumov–Gerasimenko |
E203083
|
entity |
| Predicate | closestApproachToSunEpoch |
P60984
|
FINISHED |
| Object | around August 2015 |
—
|
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: around August 2015 | Statement: [Comet 67P/Churyumov–Gerasimenko, closestApproachToSunEpoch, around August 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestApproachToSunEpoch Context triple: [Comet 67P/Churyumov–Gerasimenko, closestApproachToSunEpoch, around August 2015]
-
A.
closestApproachDate
Indicates the date on which two entities come nearest to each other in space or position.
-
B.
perihelionDate
chosen
Indicates the date on which an orbiting body reaches its closest point to the Sun in its orbital path.
-
C.
closestApproachDistance
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
D.
perihelionYear
Indicates the specific calendar year in which an object's orbit brings it to perihelion, its closest point to the Sun.
-
E.
closestApproachTarget
Indicates the entity that another entity comes nearest to during its path or motion.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea97787481909ebbaa45f59cbdaa |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.