Triple
T28353050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TBP |
E718150
|
entity |
| Predicate | contestedElectionType |
P89413
|
FINISHED |
| Object | European Parliament elections |
—
|
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: European Parliament elections | Statement: [TBP, contestedElectionType, European Parliament elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestedElectionType Context triple: [TBP, contestedElectionType, European Parliament elections]
-
A.
typeOfElectionContested
chosen
Indicates the specific kind or category of election in which an entity is competing or has competed.
-
B.
hasOfficeContested
Indicates that an individual has been a candidate for a particular public office in an election.
-
C.
contestedRace
Indicates that a race or competition is being actively challenged or disputed, typically involving multiple parties competing for the same position or outcome.
-
D.
resultContested
Indicates that the outcome or result of an event, process, or decision is being challenged or disputed by one or more parties.
-
E.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 12:47 a.m.