Triple
T30682065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Stand |
E781079
|
entity |
| Predicate | belongsToCompetitionVenue |
P21366
|
FINISHED |
| Object | Premier League venue |
—
|
LITERAL FINISHED |
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 venue | Statement: [East Stand, belongsToCompetitionVenue, Premier League venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCompetitionVenue Context triple: [East Stand, belongsToCompetitionVenue, Premier League venue]
-
A.
associatedWithCompetition
Indicates that there is a relationship or involvement between an entity and a specific competition or competitive event.
-
B.
hasAssociatedSportsVenue
Indicates that an entity is linked to a specific sports venue with which it is functionally or contextually associated.
-
C.
hasLocalRivalryVenueWith
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
-
D.
associatedWithCompetitionLevel
Indicates that something has a relationship to, or is characterized by, a particular level or tier of competition.
-
E.
locationOfCompetition
chosen
Indicates the place or venue where a competition or contest takes or 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 8:33 p.m.