Triple
T31757261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio's 8th congressional district |
E810585
|
entity |
| Predicate | BoehnerParty |
P54360
|
FINISHED |
| Object | Republican Party |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Republican Party | Statement: [Ohio's 8th congressional district, BoehnerParty, Republican Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BoehnerParty Context triple: [Ohio's 8th congressional district, BoehnerParty, Republican Party]
-
A.
republicanParty
chosen
Indicates that an entity is affiliated with, belongs to, or is a member/supporter of the Republican Party.
-
B.
partyCongress
Indicates that a political party holds or is associated with a specific congress or formal assembly.
-
C.
hadRepublicanPrimary
Indicates that a Republican Party primary election was held for a given office, race, or jurisdiction.
-
D.
oppositionPartyInCongress
Indicates that a political party serves as the primary opposing party to the ruling or majority party within a specific congress or legislative body.
-
E.
americanPartyNominee
Indicates that a person is the official nominee of a specified political party in the United States for a particular election or office.
- F. None of above.
Provenance (3 batches)
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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:29 p.m.