Triple
T28756656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Shang |
E731688
|
entity |
| Predicate | overthrownInEvent |
P22775
|
FINISHED |
| Object | Zhou conquest of Shang |
—
|
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: Zhou conquest of Shang | Statement: [King of Shang, overthrownInEvent, Zhou conquest of Shang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overthrownInEvent Context triple: [King of Shang, overthrownInEvent, Zhou conquest of Shang]
-
A.
overthrownIn
chosen
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.
-
B.
overthrown
Indicates that one entity has removed another from a position of power or authority, typically by force or political upheaval.
-
C.
overthrownByTitle
Indicates that a person holding a particular title was removed from power or deposed by another person identified by their title.
-
D.
overthrewGovernment
Indicates that an entity forcibly removed an existing government from power, typically replacing it with a new regime.
-
E.
houseOverthrown
Indicates that a ruling house or dynasty has been forcibly removed from power 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:10 a.m.