Triple
T1327464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hanson |
E28361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | president of the Continental Congress |
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: president of the Continental Congress Context triple: [John Hanson, instanceOf, president of the Continental Congress]
-
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.
Commander-in-chief
The Commander-in-chief is the highest-ranking authority responsible for the overall command, strategic direction, and ultimate decision-making of a nation's armed forces.
-
C.
President of the United States
The President of the United States is the elected head of state and government who leads the executive branch, implements and enforces federal laws, and serves as commander-in-chief of the armed forces.
-
D.
President of the Republic of Texas
The President of the Republic of Texas was the elected head of state and government of the independent Republic of Texas (1836–1846), responsible for executive leadership, diplomacy, military command, and administration of the young nation.
-
E.
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.
- 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.