Triple
T28756575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Di Xin |
E731687
|
entity |
| Predicate | reignEndReason |
P15555
|
FINISHED |
| Object | overthrown by Zhou |
—
|
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: overthrown by Zhou | Statement: [Di Xin, reignEndReason, overthrown by Zhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignEndReason Context triple: [Di Xin, reignEndReason, overthrown by Zhou]
-
A.
endOfReignReason
chosen
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
B.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
dynastyDissolutionCause
Indicates the reason or factor that led to the dissolution or end of a dynasty.
-
D.
vassalageEndedBy
Indicates that a prior vassal relationship between two entities has been terminated by a specific third party or event.
-
E.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 6:10 a.m.