Triple
T4086522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton’s light infantry battalion |
E87598
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Continental Army military unit |
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: Continental Army military unit Context triple: [Hamilton’s light infantry battalion, instanceOf, Continental Army military unit]
-
A.
Revolutionary War institution
A Revolutionary War institution is an organized body, such as a military, governmental, or civic entity, established or transformed during the American Revolution to support, administer, or legitimize the war effort and emerging nation.
-
B.
Revolutionary War institution
A Revolutionary War institution is an organized body—such as a military unit, governing council, or support organization—established during the American Revolution to coordinate, supply, or direct the war effort and emerging governance.
-
C.
Continental Army winter encampment
A Continental Army winter encampment is a temporary, fortified military settlement established during the winter months to shelter, supply, train, and maintain Revolutionary War troops in harsh conditions.
-
D.
American colonial soldier
An American colonial soldier is an armed militiaman or regular enlisted in the British American colonies who participated in local defense, frontier warfare, and major conflicts such as the French and Indian War and the American Revolutionary War.
-
E.
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.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.