Triple
T26467319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio's 21st congressional district |
E665801
|
entity |
| Predicate | partyOfNotableRepresentative |
P113489
|
FINISHED |
| Object | Democratic 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: Democratic Party | Statement: [Ohio's 21st congressional district, partyOfNotableRepresentative, Democratic Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyOfNotableRepresentative Context triple: [Ohio's 21st congressional district, partyOfNotableRepresentative, Democratic Party]
-
A.
notableMemberParty
chosen
Indicates that a political party has a member who is particularly notable or prominent within that party.
-
B.
hasRepresentativeParty
Indicates that an entity is officially represented or acted for by a particular political party or organized group.
-
C.
partnerPoliticalAffiliation
Indicates that one entity has a political affiliation that is associated with, or shared by, its partner entity.
-
D.
partyOfCandidate
Indicates the political party with which a given candidate is affiliated.
-
E.
namedForPoliticalParty
Indicates that an entity is named after or in honor of a specific political party.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 12:17 a.m.