Triple
T35517424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highbury Stadium |
E1026455
|
entity |
| Predicate | finalLeagueMatchCompetition |
P55259
|
FINISHED |
| Object | Premier League |
—
|
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: Premier League | Statement: [Highbury Stadium, finalLeagueMatchCompetition, Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLeagueMatchCompetition Context triple: [Highbury Stadium, finalLeagueMatchCompetition, Premier League]
-
A.
finalCompetitiveMatch
Indicates that a given match is the last or concluding competitive contest for the involved participant(s) or team(s).
-
B.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
-
C.
finalLeagueMatchOpponent
Indicates the opposing team or player faced in an entity’s final league match.
-
D.
finalOfficialMatch
Indicates that a given match is the last officially recognized contest or game in a defined series, season, tournament, or career.
-
E.
lastMatchCompetition
chosen
Indicates that the relationship specifies the competition in which the entity’s most recent match took place.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:04 p.m.