Triple
T32448476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 2 |
E829210
|
entity |
| Predicate | programSuccessorOf |
P62406
|
FINISHED |
| Object | Chang’e 1 |
—
|
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: Chang’e 1 | Statement: [Chang’e 2, programSuccessorOf, Chang’e 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programSuccessorOf Context triple: [Chang’e 2, programSuccessorOf, Chang’e 1]
-
A.
successorInProgram
chosen
Indicates that one element in a program directly follows another in the program’s execution or structural order.
-
B.
successorProcess
Indicates that one process directly follows another in a defined sequence or workflow.
-
C.
successorCode
Indicates that one code directly follows and replaces another code in a defined sequence or versioning scheme.
-
D.
programPredecessor
Indicates that one program temporally or logically precedes another in a sequence or hierarchy of programs.
-
E.
successorScript
Indicates that one script directly follows another in sequence, serving as its immediate successor in execution or logical order.
- 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_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:56 a.m.