Triple
T30682523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Championship 2013–14 |
E781091
|
entity |
| Predicate | seasonChampionPoints |
P185647
|
FINISHED |
| Object | 102 |
—
|
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: 102 | Statement: [Football League Championship 2013–14, seasonChampionPoints, 102]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonChampionPoints Context triple: [Football League Championship 2013–14, seasonChampionPoints, 102]
-
A.
seasonChampion
Indicates that an entity is the winner or champion of a particular season of a competition, league, or series.
-
B.
seasonChampionshipYear
Indicates the specific year in which a particular season’s championship took place or was awarded.
-
C.
bestSeasonPointsFinish
Indicates the highest points-based finishing position an entity has ever achieved in a season.
-
D.
seasonLedLeague
Indicates that, in a given season, the subject entity led the league in a particular statistical category or performance measure.
-
E.
seasonPointsRecordSet
Indicates that a new record for total points scored in a season has been achieved or established.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 29, 2026, 8:33 p.m.