Triple
T31436319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1972 Football League Cup |
E801941
|
entity |
| Predicate | finalHomeTeam |
P2620
|
FINISHED |
| Object | Stoke City 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: Stoke City F.C. | Statement: [1972 Football League Cup, finalHomeTeam, Stoke City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalHomeTeam Context triple: [1972 Football League Cup, finalHomeTeam, Stoke City F.C.]
-
A.
finalHostTeam
Indicates that a team is designated as the host team for the final match or final stage of a competition.
-
B.
homeTeam
chosen
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
C.
finalOpponentTeam
Indicates the team that serves as the last or ultimate opposing team faced in a competition, series, or event.
-
D.
awayTeam
Indicates that an entity is designated as the visiting or non-home team in a competitive event or match.
-
E.
finalTeam
Indicates that an entity is the ultimate or concluding team associated with another entity or process.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 30, 2026, 9:02 p.m.