Triple
T30682529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Championship 2013–14 |
E781091
|
entity |
| Predicate | playOffFinalLoser |
P6610
|
FINISHED |
| Object | Derby County F.C. |
—
|
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: Derby County F.C. | Statement: [Football League Championship 2013–14, playOffFinalLoser, Derby County F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playOffFinalLoser Context triple: [Football League Championship 2013–14, playOffFinalLoser, Derby County F.C.]
-
A.
semifinalLoser
Indicates that an entity lost in a semifinal round of a competition or tournament.
-
B.
finalBoutLoser
Indicates that an entity is the competitor who lost in the final bout of a match, tournament, or competition.
-
C.
finalsLosingTeam
chosen
Indicates the team that was defeated in the final match of a competition or tournament.
-
D.
postseasonSeriesLoser
Indicates that one team or competitor lost a particular postseason series to another team or competitor.
-
E.
playoffResult
Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:33 p.m.