Triple
T10028626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongzheng |
E204794
|
entity |
| Predicate | hasOrdinalNumberInQing |
P4901
|
FINISHED |
| Object | 5th 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 emperor | Statement: [Yongzheng, hasOrdinalNumberInQing, 5th emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrdinalNumberInQing Context triple: [Yongzheng, hasOrdinalNumberInQing, 5th emperor]
-
A.
ordinalNumber
chosen
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
B.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
C.
hasOrdinalSeries
Indicates that one entity belongs to, or is positioned within, an ordered sequence or series relative to other entities.
-
D.
hasNotableBearerOrdinalNumber
Indicates that an entity is associated with a notable bearer identified by a specific ordinal position (e.g., first, second, third) among others with the same name or title.
-
E.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcde51c408190afb34010b1707014 |
completed | April 2, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.