Triple
T28185501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Kang |
E716166
|
entity |
| Predicate | successorOfficeOfTitleHolder |
P119195
|
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: [Prince of Kang, successorOfficeOfTitleHolder, Emperor of China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorOfficeOfTitleHolder Context triple: [Prince of Kang, successorOfficeOfTitleHolder, Emperor of China]
-
A.
successorOfficeHolder
Indicates that one office holder directly follows another in occupying the same official position.
-
B.
successorOfficeTo
Indicates that one office or position directly follows and replaces another in an official sequence or hierarchy.
-
C.
successorOfficeEstablished
Indicates that a new office or position was formally created to replace or succeed a previous one.
-
D.
successorTitleForHolders
chosen
Indicates that one title is the official successor title that replaces or follows the titles previously held by certain holders.
-
E.
successorOfficeOfCoSovereign
Indicates that one office is the subsequent or replacement office to a previous co-sovereign office in a line of succession.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 27, 2026, 10:22 p.m.