Triple
T32448505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 2 |
E829210
|
entity |
| Predicate | achievedFirstForChina |
P21887
|
FINISHED |
| Object | first Chinese spacecraft to visit an asteroid |
—
|
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: first Chinese spacecraft to visit an asteroid | Statement: [Chang’e 2, achievedFirstForChina, first Chinese spacecraft to visit an asteroid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedFirstForChina Context triple: [Chang’e 2, achievedFirstForChina, first Chinese spacecraft to visit an asteroid]
-
A.
firstToAchieve
chosen
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
-
B.
arrivedInMainlandChina
Indicates that an entity has reached and entered the territory of mainland China from elsewhere.
-
C.
ChineseObjective
Indicates that an entity has an objective, goal, or target specifically related to China or the Chinese context.
-
D.
returnedToChina
Indicates that an entity went back to China after having been away.
-
E.
ChineseLeader
Indicates that the subject is a person who holds or has held a top political leadership position in China.
- 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.