Triple
T28094012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander, 8th Air Force |
E710035
|
entity |
| Predicate | commandsFormation |
P64547
|
FINISHED |
| Object | Eighth Air Force bomber wings |
—
|
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: Eighth Air Force bomber wings | Statement: [Commander, 8th Air Force, commandsFormation, Eighth Air Force bomber wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandsFormation Context triple: [Commander, 8th Air Force, commandsFormation, Eighth Air Force bomber wings]
-
A.
commandedFormation
chosen
Indicates that one entity held command authority over a specific military or organizational formation.
-
B.
commandedFormationType
Indicates the specific type of formation that an entity is ordered or directed to assume or maintain.
-
C.
bandFormation
Indicates the event or process by which a musical band is created or comes together as a group.
-
D.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
-
E.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 9 p.m.