Triple
T2740373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William C. McChord |
E60734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army Air Corps officer |
C449
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: U.S. Army Air Corps officer Context triple: [William C. McChord, instanceOf, U.S. Army Air Corps officer]
-
A.
United States Air Force position
A United States Air Force position is a defined role within the Air Force organizational structure that specifies an individual’s duties, responsibilities, rank requirements, and place in the chain of command to support the service’s mission.
-
B.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
C.
pioneer of military aviation
A pioneer of military aviation is an early innovator or leader who significantly advanced the development, tactics, technology, or strategic use of aircraft in armed conflict.
-
D.
aerial warfare service branch
An aerial warfare service branch is a military organization responsible for conducting and supporting combat and operational activities in the air and, increasingly, in space and cyberspace domains.
-
E.
major command of the United States Air Force
A major command of the United States Air Force is a large, top-level organizational unit responsible for directing and overseeing a broad functional or geographic segment of the Air Force’s mission, resources, and operations.
- F. None of above.
Provenance (1 batch)
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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:56 p.m.