Triple
T1327463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hanson |
E28361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Continental Congress delegate |
C3318
|
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 Congress delegate Context triple: [John Hanson, instanceOf, Continental Congress delegate]
-
A.
delegate to the Continental Congress
chosen
A delegate to the Continental Congress is an appointed or elected representative from one of the American colonies who participated in the intercolonial legislative assemblies that coordinated resistance to British rule and laid the groundwork for the United States’ independence.
-
B.
Governor of South Carolina
The Governor of South Carolina is the state's chief executive officer, responsible for implementing state laws, overseeing the executive branch, and guiding public policy and the state budget.
-
C.
revolutionary congress
A revolutionary congress is a formal assembly of representatives convened to lead, coordinate, and legitimize a political or social revolution, often drafting new governing frameworks and strategies for transformative change.
-
D.
United States congressional district
A United States congressional district is a geographically defined area within a state that elects one member to the U.S. House of Representatives.
-
E.
United States government official
A United States government official is an individual who holds an appointed or elected position within the federal, state, or local government of the United States, responsible for carrying out public duties and implementing laws and policies.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.