Triple
T33608634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 United States Senate elections |
E860925
|
entity |
| Predicate | leader1Seat |
P153542
|
FINISHED |
| Object | West Virginia |
—
|
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: West Virginia | Statement: [1988 United States Senate elections, leader1Seat, West Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader1Seat Context triple: [1988 United States Senate elections, leader1Seat, West Virginia]
-
A.
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).
-
B.
leader2SeatsChange
Indicates the change in the number of seats held by the second-leading party or leader compared to a previous reference point.
-
C.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
-
D.
seatName
chosen
Indicates the specific name or label assigned to a seat associated with an entity.
-
E.
leaderPosition
Indicates that one entity holds a leadership role or position of authority over another entity or within a specified group or organization.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:41 a.m.