Triple
T32368360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhu Wen |
E827059
|
entity |
| Predicate | overthrewRegime |
P28136
|
FINISHED |
| Object | Tang dynasty |
—
|
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: Tang dynasty | Statement: [Zhu Wen, overthrewRegime, Tang dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overthrewRegime Context triple: [Zhu Wen, overthrewRegime, Tang dynasty]
-
A.
overthrewGovernment
chosen
Indicates that an entity forcibly removed an existing government from power, typically replacing it with a new regime.
-
B.
overthrownIn
Indicates that one entity (such as a government, leader, or regime) was removed from power or defeated in a specific event, context, or time period represented by the other entity.
-
C.
governmentTypeOverthrown
Indicates that one form of government has been forcibly removed from power and replaced, typically through revolution, coup, or similar upheaval.
-
D.
replacedPreviousRegimeOf
Indicates that one regime took over and succeeded another regime, effectively displacing it from power.
-
E.
overthrown
Indicates that one entity has removed another from a position of power or authority, typically by force or political upheaval.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9f57048190819d133d4caba58e |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:50 a.m.