Triple
T6733512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Parliament elections in the Netherlands |
E153695
|
entity |
| Predicate | earlierElectionYear |
P70716
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [European Parliament elections in the Netherlands, earlierElectionYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierElectionYear Context triple: [European Parliament elections in the Netherlands, earlierElectionYear, 2014]
-
A.
previousElectionYear
chosen
Indicates the year in which the immediately preceding election for the same office, position, or body took place.
-
B.
wasEarlyElection
Indicates that an election was held earlier than its originally scheduled or expected date.
-
C.
reElectionYear
Indicates the year in which an entity is (or is scheduled to be) elected again to the same position or office.
-
D.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
E.
appliesToElectionYear
Indicates that something is relevant, valid, or in effect specifically for a given election year.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:09 p.m.