Triple
T16242279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhengtong Emperor |
E394278
|
entity |
| Predicate | restoredToThroneIn |
P73419
|
FINISHED |
| Object | 1457 |
—
|
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: 1457 | Statement: [Zhengtong Emperor, restoredToThroneIn, 1457]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredToThroneIn Context triple: [Zhengtong Emperor, restoredToThroneIn, 1457]
-
A.
restoredToThroneBy
Indicates that an entity was returned to a position of rulership or kingship through the actions or intervention of another entity.
-
B.
restoredToThrone
chosen
Indicates that an entity regains a previously held throne or royal position after having lost or been removed from it.
-
C.
regainsThroneFrom
Indicates that one entity takes back control of a throne or rulership position that had been held by another entity.
-
D.
placedOnThrone
Indicates that an entity is formally elevated to a position of rulership or authority, typically by being seated on a throne.
-
E.
ascendedToThroneIn
Indicates the time or place at which a person formally became the ruling monarch or assumed the throne.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455eeb4c81909066a8af78329ef3 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.