Triple
T32792440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wude |
E838666
|
entity |
| Predicate | successorRulerAfterEra |
P191678
|
FINISHED |
| Object | Emperor Taizong of Tang |
—
|
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: Emperor Taizong of Tang | Statement: [Wude, successorRulerAfterEra, Emperor Taizong of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorRulerAfterEra Context triple: [Wude, successorRulerAfterEra, Emperor Taizong of Tang]
-
A.
successorEraRuler
chosen
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
-
B.
successorEmperorEra
Indicates that one emperor’s era directly follows and succeeds another emperor’s era in chronological order.
-
C.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
D.
ruledLaterBy
Indicates that one entity came under the rule, governance, or authority of another entity at a later point in time.
-
E.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 1, 2026, 1:14 a.m.