Triple
T32573017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 4 |
E832565
|
entity |
| Predicate | relaySatelliteOrbit |
P12645
|
FINISHED |
| Object | Earth–Moon L2 halo 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: Earth–Moon L2 halo orbit | Statement: [Chang’e 4, relaySatelliteOrbit, Earth–Moon L2 halo orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relaySatelliteOrbit Context triple: [Chang’e 4, relaySatelliteOrbit, Earth–Moon L2 halo orbit]
-
A.
retrievedSatellite
Indicates that an entity has successfully recovered or brought back a satellite from a prior location or state.
-
B.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
C.
satelliteLocation
chosen
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
-
D.
orbitReference
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
-
E.
lastCoreConstellationSatellite
Indicates that the subject is the final satellite belonging to a defined core constellation in a sequence or deployment.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63ca2e881909f8e056c1ed181ba |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.