Triple
T36030053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongle |
E1042233
|
entity |
| Predicate | predecessorEraUsedBy |
P192787
|
FINISHED |
| Object | Emperor Jianwen |
—
|
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 Jianwen | Statement: [Yongle, predecessorEraUsedBy, Emperor Jianwen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEraUsedBy Context triple: [Yongle, predecessorEraUsedBy, Emperor Jianwen]
-
A.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
B.
predecessorRulerEraSystem
chosen
Indicates that one ruler’s era or reign immediately preceded another’s within a defined ruling system or succession framework.
-
C.
predecessorUsedUntil
Indicates that an earlier version or predecessor of an entity remained in use up to a specified time or event.
-
D.
precedesEraName
Indicates that one era occurs entirely before another era in chronological order.
-
E.
previousEraNameDerivedFrom
Indicates that the name of the current era is derived from, or based on, the name of a preceding era.
- 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_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:07 p.m.