Triple
T20961252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barside |
E516249
|
entity |
| Predicate | formerVenueComponentOf |
P142262
|
FINISHED |
| Object | English Football League matches at Layer Road |
—
|
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 at Layer Road | Statement: [Barside, formerVenueComponentOf, English Football League matches at Layer Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerVenueComponentOf Context triple: [Barside, formerVenueComponentOf, English Football League matches at Layer Road]
-
A.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
B.
legacyVenue
Indicates that a venue has historical or long-standing significance, often preserved or recognized due to its past importance or enduring role.
-
C.
venueFormerName
Indicates that a venue previously had a different official name than it has currently.
-
D.
hasFormerVenueType
Indicates that an entity previously had a specific type of venue, but that venue type is no longer current.
-
E.
venueFormerNameManaged
Indicates that a venue was previously known by a different name during the period it was managed by a particular entity.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6f134081908b1ed48ce708f3d5 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:31 p.m.