Triple
T26862880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Stand |
E676381
|
entity |
| Predicate | isPartOfCompetitionVenue |
P125043
|
FINISHED |
| Object | Scottish Professional Football League matches at Fir Park |
—
|
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: Scottish Professional Football League matches at Fir Park | Statement: [East Stand, isPartOfCompetitionVenue, Scottish Professional Football League matches at Fir Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCompetitionVenue Context triple: [East Stand, isPartOfCompetitionVenue, Scottish Professional Football League matches at Fir Park]
-
A.
isPartOfSportsVenue
chosen
Indicates that one entity is a component, section, or area contained within a larger sports venue.
-
B.
locationOfCompetition
Indicates the place or venue where a competition or contest takes or took place.
-
C.
holdsTournamentsIn
Indicates that an entity organizes or conducts tournaments at or within a specified location.
-
D.
gameVenue
Indicates the location or facility where a game or match is held.
-
E.
sportsVenueLocatedIn
Indicates that a sports venue is geographically situated within a specified location or administrative area.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 5:26 a.m.