Triple
T13188387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003–04 Premier League Golden Season |
E313917
|
entity |
| Predicate | matchesWon |
P27026
|
FINISHED |
| Object | 26 |
—
|
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: 26 | Statement: [2003–04 Premier League Golden Season, matchesWon, 26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchesWon Context triple: [2003–04 Premier League Golden Season, matchesWon, 26]
-
A.
numberOfWins
chosen
Indicates the count of times an entity has achieved victory in a relevant context or competition.
-
B.
gamesWonBy
Indicates the number of games that have been won by a particular entity in a given context.
-
C.
matchesPlayedIn
Indicates that a particular match was played in a specified location, event, or competition context.
-
D.
mostGamesWonBy
Indicates that one entity holds the record for having won the greatest number of games compared to others in a given context.
-
E.
wonAgainst
Indicates that one entity achieved victory over another in a competition, conflict, or contest.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.