Triple
T29263586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yinreng |
E741914
|
entity |
| Predicate | appointedCrownPrinceYear |
P87924
|
FINISHED |
| Object | 1675 |
—
|
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: 1675 | Statement: [Yinreng, appointedCrownPrinceYear, 1675]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedCrownPrinceYear Context triple: [Yinreng, appointedCrownPrinceYear, 1675]
-
A.
appointedCrownPrinceDate
chosen
Indicates the date on which an individual was formally appointed to the position of crown prince.
-
B.
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.
-
C.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
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.
heirApparentStartYear
Indicates the year in which an individual first became the officially recognized heir apparent to a title, position, or inheritance.
- 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_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 12:43 p.m.