Triple
T6341968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10th U.S. Cavalry Regiment |
E142648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Buffalo Soldier regiment |
C2497
|
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: Buffalo Soldier regiment Context triple: [10th U.S. Cavalry Regiment, instanceOf, Buffalo Soldier regiment]
-
A.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
parachute infantry regiment
A parachute infantry regiment is a military unit composed of soldiers trained and equipped to deploy by parachute into combat zones to conduct airborne assault, seizure, and holding of key objectives behind enemy lines.
-
C.
regiment of the United States Marine Corps
A regiment of the United States Marine Corps is a mid-level, combat-capable organizational unit typically composed of several battalions, providing command, control, and support for large-scale Marine operations.
-
D.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
E.
U.S. Army aviation battalion
A U.S. Army aviation battalion is a military unit that organizes, operates, and sustains multiple helicopter or fixed-wing aircraft companies to provide air assault, reconnaissance, transport, medical evacuation, and support capabilities to ground forces.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:30 p.m.