Triple
T34637471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Street, Bristol |
E889467
|
entity |
| Predicate | centralVenueFor |
P166905
|
FINISHED |
| Object | Bristol Rhythm & Roots Reunion |
—
|
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: Bristol Rhythm & Roots Reunion | Statement: [State Street, Bristol, centralVenueFor, Bristol Rhythm & Roots Reunion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralVenueFor Context triple: [State Street, Bristol, centralVenueFor, Bristol Rhythm & Roots Reunion]
-
A.
isCentralVenueOf
chosen
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
B.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
C.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
centeredAtVenue
Indicates that an event or activity is primarily focused on, based at, or taking place at a specific venue.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 1, 2026, 2:04 a.m.