Triple
T32792439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wude |
E838666
|
entity |
| Predicate | notableRulerDuringEra |
P33763
|
FINISHED |
| Object | Emperor Gaozu of Tang |
E208891
|
NE 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: Emperor Gaozu of Tang | Statement: [Wude, notableRulerDuringEra, Emperor Gaozu of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRulerDuringEra Context triple: [Wude, notableRulerDuringEra, Emperor Gaozu of Tang]
-
A.
notableRulerDuringService
Indicates that a specified ruler was notably in power during the time an entity (such as a person or organization) was active or providing service.
-
B.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
C.
hasFamousRuler
chosen
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
-
D.
historicalRulers
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
E.
notableMonarch
Indicates that the subject is a monarch who is distinguished or historically significant in some notable way.
- F. None of above.
Provenance (4 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35958b31d88190b9653377f1b0f14d |
completed | June 19, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:14 a.m.