Triple
T27230408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pawnee Scouts |
E682137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army Indian Scouts unit |
C52629
|
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 Indian Scouts unit Context triple: [Pawnee Scouts, instanceOf, United States Army Indian Scouts unit]
-
A.
U.S. Army cavalry squadron
A U.S. Army cavalry squadron is a battalion-sized, highly mobile combat unit organized to conduct reconnaissance, security, and offensive operations in support of larger maneuver formations.
-
B.
Canadian Army cavalry regiment
A Canadian Army cavalry regiment is a military unit historically composed of mounted soldiers and now typically equipped with armored vehicles, responsible for reconnaissance, security, and mobile combat operations.
-
C.
U.S. Army regiment
A U.S. Army regiment is a traditional military unit designation that historically grouped multiple battalions or companies under a common lineage and identity, now used primarily for organizational, administrative, and ceremonial purposes rather than as a primary tactical formation.
-
D.
Oklahoma Army National Guard unit
An Oklahoma Army National Guard unit is a state-based military organization composed of citizen-soldiers who train part-time to provide combat, support, and emergency response capabilities for both state and federal missions.
-
E.
U.S. Army task force
A U.S. Army task force is a temporary, mission-tailored organization composed of units from different branches and echelons, formed to accomplish a specific operational objective.
- F. None of above. chosen
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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:46 a.m.