Triple
T33608638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 United States Senate elections |
E860925
|
entity |
| Predicate | afterParty1Seats |
P128077
|
FINISHED |
| Object | 55 |
—
|
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: 55 | Statement: [1988 United States Senate elections, afterParty1Seats, 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterParty1Seats Context triple: [1988 United States Senate elections, afterParty1Seats, 55]
-
A.
beforeParty1Seats
Indicates that one entity takes its seat or is seated before another party (Party1) takes theirs.
-
B.
party1Seats
chosen
Indicates the number of seats held or allocated to the first party in a multi-party context.
-
C.
party2Seats
Indicates the number of seats held or allocated to the second party in a given context (such as an election or governing body).
-
D.
seatsForParty
Indicates that a seating arrangement or capacity is designated to accommodate a specific party or group.
-
E.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
- 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_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:41 a.m.