Triple
T26333575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Officer Commanding Air Forces in Iraq |
E662457
|
entity |
| Predicate | commandDomain |
P6856
|
FINISHED |
| Object | airspace over Iraq |
—
|
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: airspace over Iraq | Statement: [Air Officer Commanding Air Forces in Iraq, commandDomain, airspace over Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandDomain Context triple: [Air Officer Commanding Air Forces in Iraq, commandDomain, airspace over Iraq]
-
A.
controlDomain
Indicates that one entity has authority over, manages, or regulates the scope, behavior, or operations of another entity or system.
-
B.
commandCategory
Indicates that an action or command is classified into a specific category or type based on its function or purpose.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
commandScope
chosen
Indicates that one entity defines or limits the range, context, or extent within which another entity’s command or control is valid or applicable.
-
E.
commandName
Indicates the specific label or identifier used to denote a particular command within a system or interface.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 10:34 p.m.