Triple
T13356061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ba'athist Iraq |
E318694
|
entity |
| Predicate | tookPowerThrough |
P4209
|
FINISHED |
| Object | military coup |
—
|
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: military coup | Statement: [Ba'athist Iraq, tookPowerThrough, military coup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPowerThrough Context triple: [Ba'athist Iraq, tookPowerThrough, military coup]
-
A.
cameToPowerThrough
chosen
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
B.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
C.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
D.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd4cb008190af99c4856e76ac08 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.