Triple
T26002484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Legislature of Spain |
E646666
|
entity |
| Predicate | governingPartyAbbreviation |
P84577
|
FINISHED |
| Object | PSOE |
—
|
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: PSOE | Statement: [4th Legislature of Spain, governingPartyAbbreviation, PSOE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingPartyAbbreviation Context triple: [4th Legislature of Spain, governingPartyAbbreviation, PSOE]
-
A.
politicalPartyAbbreviation
chosen
Indicates that a political party is known or referred to by a specific abbreviated form of its name.
-
B.
governingPartyOfState
Indicates that a particular political party holds the primary governing authority over a given state.
-
C.
abbreviationOfParty
Indicates that one party’s name or designation is an abbreviation or shortened form of another party’s full name or designation.
-
D.
politicalPartyUsuallyHolding
Indicates the political party that typically holds or controls a given office, position, or jurisdiction.
-
E.
fullNameOfRulingParty
Indicates that the object is the complete official name of the political party currently in power or governing.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 22, 2026, 9 a.m.