Triple
T26308000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential election of Chile 1958 |
E661740
|
entity |
| Predicate | runnerUpAlliance |
P160561
|
FINISHED |
| Object | Frente de Acción Popular |
—
|
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: Frente de Acción Popular | Statement: [Presidential election of Chile 1958, runnerUpAlliance, Frente de Acción Popular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpAlliance Context triple: [Presidential election of Chile 1958, runnerUpAlliance, Frente de Acción Popular]
-
A.
runnerUpLeague
Indicates that an entity finished in second place in a league competition.
-
B.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
C.
runnerUpRank
Indicates the position or ranking assigned to an entity that finishes immediately after the winner (or near the top) in a competition or ordered list.
-
D.
runnerUpParty
Indicates the political party that finished in second place in an election or contest.
-
E.
runnerUpWins
Indicates that an entity finishes in second place in a competition or ranking and receives the corresponding runner-up victory or award.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee46ed08190bfba31e879318fea |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 10:20 p.m.