Triple
T22679704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Expeditionary Forces |
E560444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army field force |
C30804
|
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 Army field force Context triple: [American Expeditionary Forces, instanceOf, United States Army field force]
-
A.
United States Army field army
chosen
A United States Army field army is a large, operational-level formation typically composed of multiple corps, organized to conduct sustained, large-scale land combat operations within a theater of war.
-
B.
U.S. Army infantry division
A U.S. Army infantry division is a large, combined-arms military formation, typically consisting of several brigades and supporting units, organized and equipped primarily for ground combat operations centered on infantry forces.
-
C.
U.S. Army infantry brigade
A U.S. Army infantry brigade is a modular, combined-arms combat unit typically consisting of several infantry battalions and supporting elements, organized to conduct sustained ground operations across a range of missions.
-
D.
U.S. Army battalion
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
-
E.
U.S. Army armored division
A U.S. Army armored division is a large, combined-arms military formation centered on tanks and mechanized infantry, designed to conduct high-intensity, mobile ground combat 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:11 p.m.