Triple
T31757263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio's 8th congressional district |
E810585
|
entity |
| Predicate | BoehnerRepresentedFrom |
P144035
|
FINISHED |
| Object | 1991 |
—
|
LITERAL FINISHED |
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: 1991 | Statement: [Ohio's 8th congressional district, BoehnerRepresentedFrom, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BoehnerRepresentedFrom Context triple: [Ohio's 8th congressional district, BoehnerRepresentedFrom, 1991]
-
A.
BoehnerState
Indicates that an entity has the same U.S. state affiliation or origin as John Boehner.
-
B.
wasARepresentativeFor
chosen
Indicates that one entity served as an official representative or delegate acting on behalf of another entity.
-
C.
federalRepresentative
Indicates that one entity serves as an official representative of another entity at the federal (national) level of government.
-
D.
ALRepresentative
Indicates that one entity serves as an official representative or delegate acting on behalf of another entity.
-
E.
NLRepresentative
Indicates a relationship where one entity serves as an official representative or delegate for another within the Netherlands.
- 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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:29 p.m.