Triple
T9171700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Suzong of Tang |
E220094
|
entity |
| Predicate | succeededAfter |
P43223
|
FINISHED |
| Object | abdication of Emperor Xuanzong of Tang |
—
|
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: abdication of Emperor Xuanzong of Tang | Statement: [Emperor Suzong of Tang, succeededAfter, abdication of Emperor Xuanzong of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededAfter Context triple: [Emperor Suzong of Tang, succeededAfter, abdication of Emperor Xuanzong of Tang]
-
A.
succeededByName
Indicates that one entity is followed or replaced by another entity identified by a specific name.
-
B.
succeedsTo
chosen
Indicates that one entity takes over a role, position, or function previously held by another entity, following it in sequence or authority.
-
C.
succeedsBy
Indicates that one entity comes after or replaces another in a sequence, order, or position.
-
D.
succeedsFrom
Indicates that one entity comes after, replaces, or follows another in a sequence, order, or succession.
-
E.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae38ee48190bf783477bc37913d |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.