Triple
T16998201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wisconsin's 1st congressional district |
E412370
|
entity |
| Predicate | Paul RyanTenureStart |
P48963
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Wisconsin's 1st congressional district, Paul RyanTenureStart, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Paul RyanTenureStart Context triple: [Wisconsin's 1st congressional district, Paul RyanTenureStart, 1999]
-
A.
Roger MullinTermStart
Indicates the date or time period when Roger Mullin began his term in an official role or position.
-
B.
currentIncumbentStartYear
Indicates the year in which the entity’s current incumbent began their tenure or term in that role.
-
C.
BartGordonServedUntil
Indicates the ending date or time up to which Bart Gordon held a particular office, position, or role.
-
D.
presidentTermStart
Indicates the date or point in time when an individual officially begins serving as president of an entity.
-
E.
lastOfficeHolderStartDate
chosen
Indicates the date on which the most recent person to hold a particular office or position began their term.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37c16d081908ea5e25c992cb254 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.