Triple
T25221331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Reigart Stadium |
E631971
|
entity |
| Predicate | longStandingHomeVenueOf |
P14457
|
FINISHED |
| Object | Albion Rovers F.C. |
—
|
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: Albion Rovers F.C. | Statement: [The Reigart Stadium, longStandingHomeVenueOf, Albion Rovers F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longStandingHomeVenueOf Context triple: [The Reigart Stadium, longStandingHomeVenueOf, Albion Rovers F.C.]
-
A.
homeFieldSince
Indicates that a particular location has served as the designated home field or home venue for an entity starting from a specified point in time.
-
B.
hasSportsTeamVenueFor
chosen
Indicates that a venue serves as the home or hosting location for a particular sports team.
-
C.
significantVenueFor
Indicates that a venue plays an important or notable role in relation to a particular entity, event, or activity.
-
D.
formerHomeVenue
Indicates that a location previously served as the primary venue or home ground for an entity, but no longer holds that status.
-
E.
hasLocalRivalryVenueWith
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cbe66648190a46a29d187ab2c47 |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:03 p.m.