Triple
T24707712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018–2019 Premier League |
E611942
|
entity |
| Predicate | runnerUpPoints |
P87964
|
FINISHED |
| Object | 97 |
—
|
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: 97 | Statement: [2018–2019 Premier League, runnerUpPoints, 97]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpPoints Context triple: [2018–2019 Premier League, runnerUpPoints, 97]
-
A.
runnerUpScore
Indicates the score achieved by the participant or entity that finished in second place in a competition or ranking.
-
B.
runnersUpPoints
chosen
Indicates the number of points awarded to an entity for finishing as a runner-up 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.
runnerUpWins
Indicates that an entity finishes in second place in a competition or ranking and receives the corresponding runner-up victory or award.
-
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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:24 a.m.