Triple
T31187848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hijacking of Air France Flight 139 |
E795098
|
entity |
| Predicate | supportingState |
P207371
|
FINISHED |
| Object | Uganda |
E10768
|
NE 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: Uganda | Statement: [Hijacking of Air France Flight 139, supportingState, Uganda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportingState Context triple: [Hijacking of Air France Flight 139, supportingState, Uganda]
-
A.
supportsFormOfState
Indicates that one entity endorses, upholds, or favors a particular form or system of state governance associated with another entity.
-
B.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
-
C.
associatedState
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
-
D.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
E.
cooperatingState
Indicates that one state collaborates or works jointly with another state toward shared goals or activities.
- F. None of above. chosen
Provenance (5 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2959141f6481908bd2c49769476564 |
completed | June 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:08 p.m.