Triple
T32448491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 2 |
E829210
|
entity |
| Predicate | asteroidFlybyDate |
P22034
|
FINISHED |
| Object | 2012-12-13 |
—
|
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: 2012-12-13 | Statement: [Chang’e 2, asteroidFlybyDate, 2012-12-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asteroidFlybyDate Context triple: [Chang’e 2, asteroidFlybyDate, 2012-12-13]
-
A.
closestApproachDate
Indicates the date on which two entities come nearest to each other in space or position.
-
B.
closestApproachToJupiterDate
Indicates the date on which an object reaches its minimum distance from Jupiter during its trajectory or orbit.
-
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.
flybyDate
chosen
Indicates the date on which one object passes close to another in a flyby encounter.
-
E.
futureClosestApproachEpoch_yrFromNow
Indicates the time interval, measured in years from the present, until the next closest approach event between the related 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e822a88190a7b32d03127a2025 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.