Triple
T37691910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian legislative election 2019 |
E938827
|
entity |
| Predicate | largestPartyAbbreviation |
P84577
|
FINISHED |
| Object | ÖVP |
—
|
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: ÖVP | Statement: [Austrian legislative election 2019, largestPartyAbbreviation, ÖVP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestPartyAbbreviation Context triple: [Austrian legislative election 2019, largestPartyAbbreviation, ÖVP]
-
A.
largestParty
Indicates that the subject is the political party with the greatest size (e.g., by membership, seats, or votes) within a specified context or group.
-
B.
politicalPartyAbbreviation
chosen
Indicates that a political party is known or referred to by a specific abbreviated form of its name.
-
C.
majorParty1
Indicates that the subject entity is the primary or first major party involved in a relationship, agreement, or event.
-
D.
majorityPartyInHouse
Indicates that a given political party holds more seats than any other party in a specified legislative house.
-
E.
largestPartySeatCount
Indicates the number of seats held by the single largest party in a legislative or representative body.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.