Triple
T35949852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 EFL Championship play-off final |
E1039689
|
entity |
| Predicate | BrentfordSemi-finalOpponent |
P151082
|
FINISHED |
| Object | AFC Bournemouth |
—
|
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: AFC Bournemouth | Statement: [2021 EFL Championship play-off final, BrentfordSemi-finalOpponent, AFC Bournemouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrentfordSemi-finalOpponent Context triple: [2021 EFL Championship play-off final, BrentfordSemi-finalOpponent, AFC Bournemouth]
-
A.
BrentfordPreviousSeasonPlay-offFinal
Indicates that Brentford reached and played in the play-off final in the immediately preceding season.
-
B.
faCupSemiFinalOpponent
Indicates that one team is the opposing team faced by another team in an FA Cup semi-final match.
-
C.
BrentfordPreviousSeasonResult
Indicates the outcome or performance of Brentford in the immediately preceding season.
-
D.
homeTeamSemiFinalOpponent
chosen
Indicates the opposing team that a given home team faces in a semifinal match.
-
E.
SwanseaSemi-finalOpponent
Indicates that one entity was the opposing team Swansea faced in a semi-final match.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:07 p.m.