Triple
T2767842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ba'ath Party |
E61377
|
entity |
| Predicate | cameToPowerInSyriaBy |
P4209
|
FINISHED |
| Object | 1963 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: 1963 coup d'état | Statement: [Ba'ath Party, cameToPowerInSyriaBy, 1963 coup d'état]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameToPowerInSyriaBy Context triple: [Ba'ath Party, cameToPowerInSyriaBy, 1963 coup d'état]
-
A.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
B.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
C.
cameToPowerThrough
chosen
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
D.
lostLastTerritoryInSyria
Indicates that the entity ceased to control its final remaining territorial holding within Syria.
-
E.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
- 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_69ab4b7bab6c8190a5c2efef19a8ef34 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfc5e1c8190a5ac2c48d3eaeb0a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.