Triple
T33400720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmad Tekuder |
E855288
|
entity |
| Predicate | methodOfOverthrow |
P44028
|
FINISHED |
| Object | coup d'état |
—
|
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: coup d'état | Statement: [Ahmad Tekuder, methodOfOverthrow, coup d'état]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfOverthrow Context triple: [Ahmad Tekuder, methodOfOverthrow, coup d'état]
-
A.
overthrowMethod
chosen
Indicates the method or means by which an overthrow (such as of a government, leader, or regime) is carried out.
-
B.
overthrown
Indicates that one entity has removed another from a position of power or authority, typically by force or political upheaval.
-
C.
overthrewGovernment
Indicates that an entity forcibly removed an existing government from power, typically replacing it with a new regime.
-
D.
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.
-
E.
aimsToOverthrow
Indicates an intention or effort by one entity to remove another entity from power or authority, typically through forceful or subversive means.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:35 a.m.