Triple
T27959669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tao Qian |
E704546
|
entity |
| Predicate | successorAsGovernorOfXuProvince |
P191566
|
FINISHED |
| Object | Liu Bei |
—
|
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: Liu Bei | Statement: [Tao Qian, successorAsGovernorOfXuProvince, Liu Bei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsGovernorOfXuProvince Context triple: [Tao Qian, successorAsGovernorOfXuProvince, Liu Bei]
-
A.
successorInChina
Indicates that one entity directly follows or replaces another in a position, role, or sequence within the context of China.
-
B.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
C.
succeededByAsLieutenantGovernor
Indicates that one individual was followed in office by another individual specifically in the role of lieutenant governor.
-
D.
successorAsWesternEmperor
Indicates that one individual directly followed another in the role of Western Roman Emperor.
-
E.
succeededByAsGovernorGeneral
Indicates that one entity directly followed another in holding the position of Governor General.
- F. None of above. chosen
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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 27, 2026, 7:30 p.m.