Triple
T33106230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Libya Dawn |
E847196
|
entity |
| Predicate | coalitionComponent |
P81791
|
FINISHED |
| Object | Misrata-based militias |
—
|
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: Misrata-based militias | Statement: [Operation Libya Dawn, coalitionComponent, Misrata-based militias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionComponent Context triple: [Operation Libya Dawn, coalitionComponent, Misrata-based militias]
-
A.
coalitionBase
Indicates that one entity serves as the foundational or primary support group upon which a broader coalition or alliance is built.
-
B.
coalitionFormationFeature
chosen
Indicates the involvement of entities in forming, joining, or structuring a coalition or alliance as part of a cooperative arrangement.
-
C.
coalitionType
Indicates the specific kind or category of coalition relationship that exists between the involved entities.
-
D.
coalitionLed
Indicates that one entity serves as the primary leader or organizer of a coalition composed of multiple entities.
-
E.
coalitionPotential
Indicates the potential or likelihood that two or more entities can form a cooperative alliance or coalition.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.