Triple
T22666949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Later Han (Five Dynasties) |
E559815
|
entity |
| Predicate | yearDisestablished |
P23564
|
FINISHED |
| Object | 951 |
—
|
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: 951 | Statement: [Later Han (Five Dynasties), yearDisestablished, 951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearDisestablished Context triple: [Later Han (Five Dynasties), yearDisestablished, 951]
-
A.
disbandmentYear
chosen
Indicates the year in which an organization, group, or entity formally ceased to exist or was dissolved.
-
B.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
C.
dissolvedOrAbolished
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
D.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
E.
dissolvedOrAbolishedBy
Indicates that an entity (such as an organization, institution, or legal body) ceased to exist as a result of a specific dissolving or abolishing action carried out by another entity or authority.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781ceca08190ba1309570e81c5af |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:09 p.m.