Triple
T8811100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 611th Air Operations Center |
E209659
|
entity |
| Predicate | typeOfCommandAndControl |
P7157
|
FINISHED |
| Object | operational-level C2 |
—
|
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: operational-level C2 | Statement: [611th Air Operations Center, typeOfCommandAndControl, operational-level C2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCommandAndControl Context triple: [611th Air Operations Center, typeOfCommandAndControl, operational-level C2]
-
A.
typeOfCommand
chosen
Indicates that one entity is a specific kind or category of command in relation to another entity.
-
B.
usedCommandAndControlSystem
Indicates that an entity employed a specific command-and-control system to coordinate, manage, or direct operations or activities.
-
C.
commandAndControlBody
Indicates a relationship where one entity serves as the authoritative body that directs, manages, and oversees the operations or actions of another entity.
-
D.
commandType
Indicates the specific kind or category of command being issued or executed in the relationship.
-
E.
controlUnitType
Indicates the specific kind or category of control unit associated with or assigned to an entity.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fed18f8819087b0282bf8c4208c |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.