Triple
T5150136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Texas Infantry |
E116172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States Army infantry 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: Confederate States Army infantry regiment Context triple: [1st Texas Infantry, instanceOf, Confederate States Army infantry 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.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
C.
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.
-
D.
United States Army formation type
A United States Army formation type is a standardized organizational structure that defines the size, composition, and command hierarchy of Army units for specific operational roles and missions.
-
E.
component of the United States Army
A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:43 p.m.