Triple
T20642804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Line |
E507273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Continental Army line |
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 line Context triple: [New Jersey Line, instanceOf, Continental Army line]
-
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.
Continental Army regiment
chosen
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.
-
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.
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.
-
E.
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.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.