Triple
T32600263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 5 |
E833345
|
entity |
| Predicate | EarthLandingSite |
P174071
|
FINISHED |
| Object | Siziwang Banner, Inner Mongolia |
—
|
NE NERFINISHED |
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: Siziwang Banner, Inner Mongolia | Statement: [Chang’e 5, EarthLandingSite, Siziwang Banner, Inner Mongolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EarthLandingSite Context triple: [Chang’e 5, EarthLandingSite, Siziwang Banner, Inner Mongolia]
-
A.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
B.
firstLandingSite
Indicates the location where an entity initially arrives, lands, or touches down before any subsequent movements or landings.
-
C.
wasLandingSiteOf
chosen
Indicates that a location served as the site where a landing event (such as a spacecraft, aircraft, or vehicle) took place.
-
D.
lunarLandingSiteDetail
Indicates the specific characteristics or contextual information associated with a lunar landing site.
-
E.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:05 a.m.