Triple
T37348918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Stand |
E927262
|
entity |
| Predicate | isPartOfCompetitionVenueFor |
P21366
|
FINISHED |
| Object | English football league matches |
—
|
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: English football league matches | Statement: [West Stand, isPartOfCompetitionVenueFor, English football league matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCompetitionVenueFor Context triple: [West Stand, isPartOfCompetitionVenueFor, English football league matches]
-
A.
locationOfCompetition
chosen
Indicates the place or venue where a competition or contest takes or took place.
-
B.
holdsTournamentsIn
Indicates that an entity organizes or conducts tournaments at or within a specified location.
-
C.
hasLocalRivalryVenueWith
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
-
D.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
-
E.
playsInArenaLocatedIn
Indicates that an entity performs or participates in events within an arena that is geographically located in a specified 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 3, 2026, 4:16 p.m.