Triple
T29263590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yinreng |
E741914
|
entity |
| Predicate | deposedAgainAsCrownPrince |
P166783
|
FINISHED |
| Object | 1712 |
—
|
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: 1712 | Statement: [Yinreng, deposedAgainAsCrownPrince, 1712]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deposedAgainAsCrownPrince Context triple: [Yinreng, deposedAgainAsCrownPrince, 1712]
-
A.
deposedAsCrownPrince
chosen
Indicates that an individual was removed from the position or status of crown prince.
-
B.
reignAsPrinceEnd
Indicates the point in time or event at which an individual’s tenure or role as a prince comes to an end.
-
C.
reignAsCrownPrinceFrom
Indicates the period during which a person holds and exercises the official status and role of crown prince of a particular realm or title.
-
D.
appointedCrownPrinceBy
Indicates that one entity is formally designated as crown prince by another entity, typically an authority such as a monarch or governing body.
-
E.
successorAsCrownPrince
Indicates that one person becomes the next crown prince, directly succeeding another in that royal position.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664dd47488190946f9a3f9c4a7d24 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:43 p.m.