Triple
T25980048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republican presidential nomination 1948 |
E646041
|
entity |
| Predicate | frontRunner |
P77415
|
FINISHED |
| Object | Thomas E. Dewey |
—
|
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: Thomas E. Dewey | Statement: [Republican presidential nomination 1948, frontRunner, Thomas E. Dewey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontRunner Context triple: [Republican presidential nomination 1948, frontRunner, Thomas E. Dewey]
-
A.
frontRunnerAtStart
Indicates that an entity is the leading competitor or in first position at the beginning of an event or process.
-
B.
eventualFrontRunner
Indicates that an entity is expected or predicted to become the leading or most successful one among a set of competitors in the future.
-
C.
frontRunnerAtConvention
chosen
Indicates that an individual is the leading candidate in delegate support or perceived likelihood of nomination at a political party’s convention.
-
D.
runnerUpDriver
Indicates that one driver finished in second place relative to others in a race or competition.
-
E.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 8:54 a.m.