Triple
T23690127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 Spanish general election |
E585273
|
entity |
| Predicate | wasFreeAndFair |
P40674
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [1979 Spanish general election, wasFreeAndFair, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFreeAndFair Context triple: [1979 Spanish general election, wasFreeAndFair, yes]
-
A.
electoralFreedom
chosen
Indicates the extent to which individuals and groups can participate in elections—such as voting, running for office, and campaigning—without undue restriction, coercion, or manipulation.
-
B.
wasCloseElection
Indicates that an election was decided by a very small margin between candidates or options.
-
C.
electoralDignity
Indicates a relationship where an entity holds or is associated with an official electoral office, rank, or honor within a political or voting system.
-
D.
wasEarlyElection
Indicates that an election was held earlier than its originally scheduled or expected date.
-
E.
hadRightToElect
Indicates that an entity possessed the legal or formal authority to choose or vote for another entity in an election or selection process.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c16af08190b2f4d126c60a7e75 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.