Triple
T33076245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aisin-Gioro Yinzhen |
E846369
|
entity |
| Predicate | numberInDynasty |
P170010
|
FINISHED |
| Object | 5th Qing emperor |
—
|
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: 5th Qing emperor | Statement: [Aisin-Gioro Yinzhen, numberInDynasty, 5th Qing emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInDynasty Context triple: [Aisin-Gioro Yinzhen, numberInDynasty, 5th Qing emperor]
-
A.
eraNumberInDynasty
Indicates that a specific era is identified by and associated with a particular numbered position within a dynasty.
-
B.
kingNumberWithinDynasty
chosen
Indicates the ordinal position of a king within a specific dynasty, expressing which numbered ruler he is in that dynastic sequence.
-
C.
dynasticNumber
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
D.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
E.
eraSequenceWithinDynasty
Indicates that one historical era occurs in a specific ordered position relative to another era within the same dynasty.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
Created at: May 1, 2026, 1:25 a.m.