Triple
T1695115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Church |
E36639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial American military officer |
C4839
|
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: colonial American military officer Context triple: [Benjamin Church, instanceOf, colonial American military officer]
-
A.
American colonial soldier
chosen
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.
-
B.
American Revolutionary War figure
An American Revolutionary War figure is an individual who played a significant political, military, or ideological role in the struggle for independence of the thirteen American colonies from British rule between 1775 and 1783.
-
C.
Revolutionary War leader
A Revolutionary War leader is an individual who organizes, commands, or significantly influences military and political efforts to overthrow an existing regime and establish a new order during a revolutionary conflict.
-
D.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
E.
Dutch general
A Dutch general is a high-ranking military officer from the Netherlands responsible for leading and overseeing major army operations, strategy, and personnel.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.