Triple
T36030052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongle |
E1042233
|
entity |
| Predicate | successorEraUsedBy |
P29666
|
FINISHED |
| Object | Emperor Hongxi |
—
|
NE NERFINISHED |
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: Emperor Hongxi | Statement: [Yongle, successorEraUsedBy, Emperor Hongxi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEraUsedBy Context triple: [Yongle, successorEraUsedBy, Emperor Hongxi]
-
A.
successorEmperorEra
Indicates that one emperor’s era directly follows and succeeds another emperor’s era in chronological order.
-
B.
successorEraUnderSameEmperor
Indicates that one historical era directly follows another while both occur under the reign of the same emperor.
-
C.
followsEra
chosen
Indicates that one time period or era comes directly after another in chronological order.
-
D.
predecessorRulerEraSystem
Indicates that one ruler’s era or reign immediately preceded another’s within a defined ruling system or succession framework.
-
E.
successorEraRuler
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: May 3, 2026, 4:07 p.m.