Triple
T28801573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongxi |
E727249
|
entity |
| Predicate | sovereignTitleDuringEra |
P163818
|
FINISHED |
| Object | Emperor of China |
—
|
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 of China | Statement: [Yongxi, sovereignTitleDuringEra, Emperor of China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereignTitleDuringEra Context triple: [Yongxi, sovereignTitleDuringEra, Emperor of China]
-
A.
sovereignTitleUntil
Indicates that an entity held a particular sovereign title or rulership status continuously up to a specified end date or point in time.
-
B.
titleHeldWhileMonarchReigns
chosen
Indicates that one entity holds a specific title during the period in which another entity is reigning as monarch.
-
C.
monarchTitleAtEstablishment
Indicates the formal royal title held by a monarch at the time a political entity or state was first established.
-
D.
longestReigningTitle
Indicates that a person or entity holds the record for having possessed a particular title or position for the greatest length of time compared to all others.
-
E.
titleHeldByRulers
Indicates that a specific title is or was borne by one or more rulers.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:27 a.m.