Triple
T3461465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongle Emperor |
E73034
|
entity |
| Predicate | ordinalInDynasty |
P24058
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Yongle Emperor, ordinalInDynasty, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinalInDynasty Context triple: [Yongle Emperor, ordinalInDynasty, 3]
-
A.
dynasticNumber
chosen
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
B.
positionInLineOfSuccessionAtBirth
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
C.
hasDynasticOrder
Indicates that there exists a specific sequence or hierarchy of dynasties or ruling lines associated with the subject.
-
D.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
-
E.
dynasticSeat
Indicates that a particular location serves as the principal seat of power or ruling center for a specific dynasty or ruling family.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae745e081909007cd3a664c57f3 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.