Triple
T33608635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 United States Senate elections |
E860925
|
entity |
| Predicate | leader2Seat |
P181280
|
FINISHED |
| Object | Kansas |
—
|
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: Kansas | Statement: [1988 United States Senate elections, leader2Seat, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader2Seat Context triple: [1988 United States Senate elections, leader2Seat, Kansas]
-
A.
leader2SeatsChange
Indicates the change in the number of seats held by the second-leading party or leader compared to a previous reference point.
-
B.
leader1SeatsChange
Indicates a change in the number of seats held by the first leader in a given context (such as an election or governing body).
-
C.
leaderPosition
Indicates that one entity holds a leadership role or position of authority over another entity or within a specified group or organization.
-
D.
leader4SeatsChange
Indicates a change in the number of seats held that is attributed to the leader.
-
E.
leader3SeatsChange
Indicates the change in the number of seats held by the third-ranked leader (or leading entity) between two points in time.
- F. None of above. chosen
Provenance (4 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1:41 a.m.