Triple
T37105311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4179 Toutatis |
E918823
|
entity |
| Predicate | closeApproachToEarth |
P13779
|
FINISHED |
| Object | 1992-12-08 |
—
|
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: 1992-12-08 | Statement: [4179 Toutatis, closeApproachToEarth, 1992-12-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closeApproachToEarth Context triple: [4179 Toutatis, closeApproachToEarth, 1992-12-08]
-
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.
closestApproachTarget
Indicates the entity that another entity comes nearest to during its path or motion.
-
C.
closestApproachDate
chosen
Indicates the date on which two entities come nearest to each other in space or position.
-
D.
closeApproachToEarthFrequency
Indicates how often an object makes a close approach to Earth within a specified time period.
-
E.
hasCloseApproachGeometry
Indicates that there exists detailed geometric information describing the spatial configuration and trajectory of a close approach event between two entities.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:14 p.m.