Triple
T26282514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42nd Air Division |
E661037
|
entity |
| Predicate | oversawUnitsBasedAt |
P166145
|
FINISHED |
| Object | McCoy Air Force Base |
—
|
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: McCoy Air Force Base | Statement: [42nd Air Division, oversawUnitsBasedAt, McCoy Air Force Base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversawUnitsBasedAt Context triple: [42nd Air Division, oversawUnitsBasedAt, McCoy Air Force Base]
-
A.
oversawUnitType
Indicates that an entity had supervisory or managerial responsibility over a particular type or category of unit.
-
B.
oversawUnitThatBecame
Indicates that one entity supervised or managed a unit that later transformed into, merged into, or was reconstituted as another unit.
-
C.
overseesOffice
Indicates that one entity has managerial or supervisory responsibility for the operations or activities of a particular office.
-
D.
oversawArea
Indicates that one entity had supervisory or managerial responsibility over a particular area, region, or domain associated with another entity.
-
E.
hasHindquartersOf
Indicates that one entity possesses or exhibits the hindquarters characteristic or form of another entity.
- F. None of above. chosen
Provenance (4 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 26, 2026, 10:01 p.m.