Triple
T35575759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford Minutemen |
E1028069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Revolutionary War militia unit |
C56754
|
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 unit Context triple: [Bedford Minutemen, instanceOf, American Revolutionary War militia unit]
-
A.
American Revolutionary War military unit
chosen
An American Revolutionary War military unit is an organized group of soldiers from the Continental Army, state militias, or allied forces that fought in coordinated operations against British and Loyalist forces between 1775 and 1783.
-
B.
Patriot militia
A patriot militia is a civilian-based, non-professional armed group organized to defend its homeland or political cause, typically operating independently of a formal standing army.
-
C.
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.
-
D.
Continental Army regiment
A Continental Army regiment is a military unit composed of several companies of soldiers organized under a unified command to serve as a primary operational formation in the Continental Army during the American Revolutionary War.
-
E.
Loyalist cavalry unit
A Loyalist cavalry unit is a mounted military force composed of soldiers who remain steadfastly aligned with and fight on behalf of an established authority or ruling power during periods of conflict or rebellion.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.