Triple
T32368244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tang dynasty |
E827056
|
entity |
| Predicate | finalEmperor |
P130511
|
FINISHED |
| Object | Emperor Ai 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 Ai of Tang | Statement: [Tang dynasty, finalEmperor, Emperor Ai of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalEmperor Context triple: [Tang dynasty, finalEmperor, Emperor Ai of Tang]
-
A.
finalEmperorOf
chosen
Indicates that one entity is the last ruler to hold the imperial title over another entity (such as a state, dynasty, or empire).
-
B.
endEmperor
Indicates the point or event at which an individual's tenure or status as emperor comes to an end.
-
C.
coEmperorEnd
Indicates that one entity’s tenure as co-emperor with another entity comes to an end at a specific point in time.
-
D.
fourthEmperor
Indicates that one entity is the fourth emperor in a specified imperial succession relative to another entity (such as a dynasty, state, or realm).
-
E.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 1, 2026, 12:50 a.m.