Triple
T32476575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese space program |
E829990
|
entity |
| Predicate | firstLunarLander |
P82944
|
FINISHED |
| Object | Chang'e 3 |
E830857
|
NE 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: Chang'e 3 | Statement: [Chinese space program, firstLunarLander, Chang'e 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLunarLander Context triple: [Chinese space program, firstLunarLander, Chang'e 3]
-
A.
firstSuccessfulLander
Indicates that the subject entity is the earliest one to have successfully landed on the specified target or within the given context.
-
B.
plannedFirstLunarLanding
Indicates that an entity is responsible for organizing or scheduling the earliest intended mission to land on the Moon.
-
C.
firstLunarLandingLaunchVehicle
Indicates the launch vehicle used to carry out the first lunar landing mission for a given space program or mission.
-
D.
firstSoftLandingBy
chosen
Indicates that the subject is the first entity to successfully achieve a soft landing on the object.
-
E.
firstLandingAttemptOn
Indicates that an entity makes its initial attempt to land on another entity or location.
- F. None of above.
Provenance (4 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34a78f537481909b7b3b9e58b496ab |
completed | June 19, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:58 a.m.