Triple
T24194241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2009–10 |
E599783
|
entity |
| Predicate | biggestWin |
P149395
|
FINISHED |
| Object | Chelsea 8–0 Wigan Athletic |
—
|
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: Chelsea 8–0 Wigan Athletic | Statement: [Premier League 2009–10, biggestWin, Chelsea 8–0 Wigan Athletic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biggestWin Context triple: [Premier League 2009–10, biggestWin, Chelsea 8–0 Wigan Athletic]
-
A.
largestWin
chosen
Indicates the relationship where one entity achieves its greatest margin or most significant victory over another in a competitive context.
-
B.
largestWinDate
Indicates the date on which an entity achieved its largest or most significant win.
-
C.
mostOverallWinsRecord
Indicates that the subject holds the record for having the greatest total number of wins compared to all others in the relevant context.
-
D.
mostConsecutiveWinsCount
Indicates the highest number of wins achieved in a row within a given sequence or context.
-
E.
mostConsecutiveWinsPlayer
Indicates the player who holds the record for the highest number of consecutive wins within a given context or competition.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24947948190b609a39a2b8828ad |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.