Triple
T10675104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Ashe |
E251595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Revolutionary-era politician |
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: American Revolutionary-era politician Context triple: [Samuel Ashe, instanceOf, American Revolutionary-era politician]
-
A.
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.
-
B.
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.
-
C.
Puritan statesman
A Puritan statesman is a political leader whose governance and public life are deeply shaped by Puritan religious principles, emphasizing moral rigor, communal discipline, and covenantal responsibility.
-
D.
North Carolina statesman
A North Carolina statesman is a respected political leader from North Carolina who demonstrates long-term public service, integrity, and significant influence on the state’s governance and policy.
-
E.
colonial political leader
A colonial political leader is an individual who holds formal or informal authority within a colony and influences governance, policy, and relations between the colonizing power and the colonized population.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:09 p.m.