Triple
T22192413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunterdon County militia |
E548461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Revolutionary War militia |
C9772
|
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: American Revolutionary War militia Context triple: [Hunterdon County militia, instanceOf, American Revolutionary War militia]
-
A.
Continental Army soldier
A Continental Army soldier is an enlisted or commissioned member of the colonial military force formed by the Second Continental Congress to fight against British rule during the American Revolutionary War.
-
B.
American Revolutionary War engagement
An American Revolutionary War engagement is a specific military encounter or battle between opposing forces during the American Revolution, typically involving organized combat over strategic objectives.
-
C.
private colonial army
A private colonial army is a non-state military force organized and funded by a colonial power or its chartered companies to secure territory, enforce control, and protect economic interests in colonized regions.
-
D.
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.
-
E.
Revolutionary War institution
chosen
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.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.