Triple
T31876271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic Connections festival events |
E813751
|
entity |
| Predicate | alsoUseVenue |
P53622
|
FINISHED |
| Object | Old Fruitmarket, Glasgow |
—
|
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: Old Fruitmarket, Glasgow | Statement: [Celtic Connections festival events, alsoUseVenue, Old Fruitmarket, Glasgow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoUseVenue Context triple: [Celtic Connections festival events, alsoUseVenue, Old Fruitmarket, Glasgow]
-
A.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
B.
homeVenueAlsoUsedBy
chosen
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
C.
associatedWithVenueSecondaryUse
Indicates that an entity has a secondary or supplementary association with a particular venue, beyond its primary or main use.
-
D.
usualVenueSince
Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
-
E.
willUseExistingVenues
Indicates that the subject plans to utilize venues that already exist rather than constructing or selecting new ones.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0a7d9888190bf1df991aa1faad9 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:55 p.m.