Triple
T30681987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Power Stadium |
E781076
|
entity |
| Predicate | homeTeamLeagueDuring2015–16 |
P17373
|
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: [King Power Stadium, homeTeamLeagueDuring2015–16, Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamLeagueDuring2015–16 Context triple: [King Power Stadium, homeTeamLeagueDuring2015–16, Premier League]
-
A.
homeTeamLeagueDuringName
Indicates the name of the league in which the home team is participating during a specified time period.
-
B.
leagueOfHomeTeam
chosen
Indicates the league or competition in which the home team participates or is affiliated.
-
C.
homeTeamForGame5
Indicates which team is designated as the home team in game 5 of a series or schedule.
-
D.
homeTeamSince
Indicates the point in time from which a particular team has been designated as the home team for a given context or venue.
-
E.
locationTeam1Home
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:33 p.m.