Triple
T24706692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Florida, Glasgow |
E611911
|
entity |
| Predicate | sportsVenueUse |
P39293
|
FINISHED |
| Object | football matches at Hampden 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: football matches at Hampden Park | Statement: [Mount Florida, Glasgow, sportsVenueUse, football matches at Hampden Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsVenueUse Context triple: [Mount Florida, Glasgow, sportsVenueUse, football matches at Hampden Park]
-
A.
sportsVenueFor
chosen
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
B.
ownsSportsVenue
Indicates that one entity possesses legal ownership or controlling property rights over a sports venue used for athletic or sporting events.
-
C.
gameVenue
Indicates the location or facility where a game or match is held.
-
D.
openedAsSportsVenue
Indicates that a place or facility began its operation specifically for hosting sports events or activities.
-
E.
sportsFacility
Indicates that one entity is a sports facility where sports or physical activities can take place for the other entity.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:24 a.m.