Triple
T16765351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force ceremonial guardsmen |
E407449
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Air Force personnel |
C7744
|
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: United States Air Force personnel Context triple: [Air Force ceremonial guardsmen, instanceOf, United States Air Force personnel]
-
A.
United States Air Force airman
A United States Air Force airman is an enlisted or commissioned member of the U.S. Air Force responsible for supporting and executing air, space, and cyberspace operations in defense of national security.
-
B.
American military personnel
chosen
American military personnel are individuals who serve in the United States Armed Forces, including the Army, Navy, Air Force, Marine Corps, Space Force, and Coast Guard, in roles ranging from combat and support to technical and administrative duties.
-
C.
Royal Australian Air Force personnel
Individuals who serve or have served in the Royal Australian Air Force, fulfilling military, technical, and support roles in Australia's air and space defense forces.
-
D.
former air force
A former air force is a previously active national military aviation branch that has been disbanded, merged, or otherwise ceased to operate as an independent air service.
-
E.
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.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.