Triple
T18716286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Rhode Island Regiment |
E457648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Continental Army regiment |
C40679
|
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: Continental Army regiment Context triple: [1st Rhode Island Regiment, instanceOf, Continental Army regiment]
-
A.
Continental Army brigade formation
A Continental Army brigade formation was a tactical military unit composed of several regiments organized under a brigadier general, arranged on the battlefield to coordinate infantry, artillery, and support elements during the American Revolutionary War.
-
B.
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.
-
C.
logistic regiment
A logistic regiment is a military unit specialized in planning, coordinating, and executing the supply, transportation, maintenance, and support services necessary to sustain combat and support forces.
-
D.
lancer regiment
A lancer regiment is a cavalry unit historically equipped with lances, organized for fast, shock-oriented charges and reconnaissance on the battlefield.
-
E.
field regiment
A field regiment is a military unit, typically part of an army’s artillery or armored forces, organized and equipped to provide mobile, tactical firepower and support on the battlefield.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.