Triple
T32005454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libyan airbase at Ouadi Doum |
E817252
|
entity |
| Predicate | controlledDuringConflict |
P57414
|
FINISHED |
| Object | Libya |
—
|
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: Libya | Statement: [Libyan airbase at Ouadi Doum, controlledDuringConflict, Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledDuringConflict Context triple: [Libyan airbase at Ouadi Doum, controlledDuringConflict, Libya]
-
A.
implementedDuringConflict
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
-
B.
statusDuringConflict
chosen
Indicates the role, condition, or standing an entity held throughout a specified conflict or period of hostilities.
-
C.
usedByDuringConflict
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more parties.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 12:15 a.m.