Triple
T4900728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo convention of 1848 |
E109791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States political event |
C238
|
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: United States political event Context triple: [Buffalo convention of 1848, instanceOf, United States political event]
-
A.
United States legal history event
A United States legal history event is a significant occurrence—such as a court decision, statute, constitutional amendment, or legal controversy—that materially shaped the development, interpretation, or application of American law.
-
B.
United States military history event
A United States military history event is a significant occurrence involving U.S. armed forces that influences the nation’s military development, strategy, policy, or historical trajectory.
-
C.
political event
chosen
A political event is a planned or spontaneous occurrence involving political actors, institutions, or the public that aims to influence, express, or respond to political power, policy, or public opinion.
-
D.
United States federal government action
A United States federal government action is any formal decision, policy, regulation, enforcement measure, or operation undertaken by a federal branch or agency under constitutional or statutory authority to influence public affairs or implement federal law.
-
E.
era in United States history
An era in United States history is a distinct time period characterized by particular political, social, economic, and cultural conditions or transformative events that differentiate it from other periods.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:28 p.m.