Triple
T32896754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberian general election, 2017 |
E841493
|
entity |
| Predicate | resultAcceptedByRunnerUp |
P190692
|
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: [Liberian general election, 2017, resultAcceptedByRunnerUp, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAcceptedByRunnerUp Context triple: [Liberian general election, 2017, resultAcceptedByRunnerUp, yes]
-
A.
runnerUpWins
Indicates that an entity finishes in second place in a competition or ranking and receives the corresponding runner-up victory or award.
-
B.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
C.
runnerUpFinalRecord
Indicates the final performance or outcome record associated with the entity that finished as runner-up in a competition or event.
-
D.
conferenceOfRunnerUp
Indicates the conference or league affiliation to which the runner-up entity belongs.
-
E.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 1, 2026, 1:18 a.m.