Triple
T3810261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Osgood |
E93115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Revolutionary War officer |
C7216
|
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: Revolutionary War officer Context triple: [Samuel Osgood, instanceOf, Revolutionary War officer]
-
A.
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.
-
B.
American Revolutionary War figure
chosen
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.
English colonial military leader
An English colonial military leader is a commander from England who directed armed forces and strategic operations in overseas colonies to expand, secure, or administer imperial control.
-
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
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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:16 p.m.