Triple
T32448477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 2 |
E829210
|
entity |
| Predicate | programPredecessorOf |
P25183
|
FINISHED |
| Object | Chang’e 3 |
—
|
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 3 | Statement: [Chang’e 2, programPredecessorOf, Chang’e 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programPredecessorOf Context triple: [Chang’e 2, programPredecessorOf, Chang’e 3]
-
A.
programPredecessor
chosen
Indicates that one program temporally or logically precedes another in a sequence or hierarchy of programs.
-
B.
predecessorCode
Indicates that one code directly precedes another code in a defined sequence or versioning order.
-
C.
testingPredecessor
Indicates that one entity performed testing or validation activities prior to, and potentially enabling or informing, the testing performed by another entity.
-
D.
predecessorInstrumentOf
Indicates that one instrument previously existed or was used in a role, function, or context that was later taken over or continued by another instrument.
-
E.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
- 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_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 12:56 a.m.