Triple
T25517838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Madrilenian regional election |
E639557
|
entity |
| Predicate | ppSeatChange |
P84103
|
FINISHED |
| Object | +35 |
—
|
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: +35 | Statement: [2021 Madrilenian regional election, ppSeatChange, +35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ppSeatChange Context triple: [2021 Madrilenian regional election, ppSeatChange, +35]
-
A.
thirdPartySeatChange
Indicates that a passenger’s seat assignment is changed by someone other than the passenger or the operating carrier (i.e., by a third party).
-
B.
snpNetSeatChange
chosen
Indicates a change in the number of seats held by a political party or group in a legislative body between two points in time.
-
C.
movedSeatTo
Indicates that one entity changed another entity’s seating position from one place to another.
-
D.
movedSeatFrom
Indicates that an entity changed its seating position from a specified original seat or location to another.
-
E.
secondPartySeatChange
Indicates that the second party’s assigned seat has been changed from one seat to another.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8339a8081908738ba23158091c9 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:57 p.m.