Triple
T27348980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Polish presidential election |
E684303
|
entity |
| Predicate | runnerUpPoliticalPosition |
P163485
|
FINISHED |
| Object | conservative |
—
|
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: conservative | Statement: [2010 Polish presidential election, runnerUpPoliticalPosition, conservative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpPoliticalPosition Context triple: [2010 Polish presidential election, runnerUpPoliticalPosition, conservative]
-
A.
runnerUpParty
Indicates the political party that finished in second place in an election or contest.
-
B.
electoralPosition
Indicates that an entity holds, has held, or is a candidate for a specific role or office within an electoral or political system.
-
C.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
D.
popularVoteRunnerUp
Indicates that one entity is the candidate who received the second-highest number of votes in a popular vote for the other entity’s election or contest.
-
E.
featuredCandidate
Indicates that a particular candidate is highlighted or given special prominence relative to others.
- F. None of above. chosen
Provenance (4 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 11:47 a.m.