Triple
T63001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armor Branch |
E1250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army branch |
C408
|
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 branch Context triple: [Armor Branch, instanceOf, United States Army branch]
-
A.
branch of the United States Army
chosen
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.
-
B.
branch of the United States Armed Forces
A branch of the United States Armed Forces is a distinct military service component (such as the Army, Navy, Air Force, Marine Corps, Space Force, or Coast Guard) with its own mission, structure, and responsibilities for national defense and security.
-
C.
land warfare service branch
A land warfare service branch is a military organization primarily responsible for conducting combat and support operations on land using ground forces and associated assets.
-
D.
United States Army installation
A United States Army installation is a designated military facility, base, or post that supports the housing, training, operations, logistics, and administration of Army personnel and equipment.
-
E.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.