Triple
T25892171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayresome Park |
E652365
|
entity |
| Predicate | finalLeagueMatchOpponent |
P166599
|
FINISHED |
| Object | Luton Town |
—
|
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: Luton Town | Statement: [Ayresome Park, finalLeagueMatchOpponent, Luton Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLeagueMatchOpponent Context triple: [Ayresome Park, finalLeagueMatchOpponent, Luton Town]
-
A.
finalOpponentTeam
Indicates the team that serves as the last or ultimate opposing team faced in a competition, series, or event.
-
B.
finalOpponentOf
Indicates that one entity serves as the last or ultimate opponent faced by another entity in a sequence of confrontations or competitions.
-
C.
leagueCupFinalOpponent
Indicates that one entity is the opponent faced by another entity in the final match of a league cup competition.
-
D.
playoffOpponent
Indicates that two entities are matched to compete against each other in a playoff round or series.
-
E.
finalOpponentInstitution
Indicates the institution that served as the final opposing side in a competition, match, or contest involving the subject.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 22, 2026, 8:22 a.m.