Triple
T24853208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigerian Air Force Special Operations Command |
E621948
|
entity |
| Predicate | operatesBeyond |
P121954
|
FINISHED |
| Object | Nigeria |
—
|
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: Nigeria | Statement: [Nigerian Air Force Special Operations Command, operatesBeyond, Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesBeyond Context triple: [Nigerian Air Force Special Operations Command, operatesBeyond, Nigeria]
-
A.
operatesOutsideOf
chosen
Indicates that an entity performs its activities or functions beyond the boundaries or jurisdiction of a specified entity or context.
-
B.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
C.
operatesBeyondRegion
Indicates that an entity conducts activities or exerts influence outside a specified geographic region.
-
D.
operatedOutside
Indicates that an entity performed operations or activities beyond a defined boundary, jurisdiction, or designated area.
-
E.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 5:21 a.m.