Triple
T16467649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianshun Emperor |
E399975
|
entity |
| Predicate | eraChronology |
P122893
|
FINISHED |
| Object | succeeded Zhengtong era |
—
|
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: succeeded Zhengtong era | Statement: [Tianshun Emperor, eraChronology, succeeded Zhengtong era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraChronology Context triple: [Tianshun Emperor, eraChronology, succeeded Zhengtong era]
-
A.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologyIncludes
Indicates that a broader chronological sequence or timeline encompasses a specific time span, event, or period as part of it.
-
C.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
D.
chronologicalRange
Indicates the temporal span or period over which something occurs, is valid, or is relevant.
-
E.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
- F. None of above. chosen
Provenance (4 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dcd707081908fb7ca91a8c09e0a |
completed | April 18, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:11 a.m.