Triple
T32448488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 2 |
E829210
|
entity |
| Predicate | lunarOrbitPeriseleneAltitude |
P24802
|
FINISHED |
| Object | approximately 15 km |
—
|
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: approximately 15 km | Statement: [Chang’e 2, lunarOrbitPeriseleneAltitude, approximately 15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lunarOrbitPeriseleneAltitude Context triple: [Chang’e 2, lunarOrbitPeriseleneAltitude, approximately 15 km]
-
A.
perigeeLocation
Indicates the location in an orbit where an object is at its closest point to the body it is orbiting (its perigee).
-
B.
perigee
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
C.
closestApproachToMoon
chosen
Indicates the point or distance at which an object comes nearest to the Moon along its trajectory or orbit.
-
D.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
E.
orbitFirstReached
Indicates the point in time or event when an object first successfully enters into a specified orbit.
- 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.