Triple
T34043923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Blues Records |
E873026
|
entity |
| Predicate | associatedVenueChain |
P134947
|
FINISHED |
| Object | House of Blues |
E1137598
|
NE 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: House of Blues | Statement: [House of Blues Records, associatedVenueChain, House of Blues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedVenueChain Context triple: [House of Blues Records, associatedVenueChain, House of Blues]
-
A.
venueAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between an event, activity, or entity and a particular venue or location.
-
B.
isCentralVenueOf
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
C.
coVenueWith
Indicates that two events or activities take place at the same venue or location.
-
D.
venueAlsoKnownAs
Indicates that a venue has an alternative name or alias by which it is also known.
-
E.
sisterVenue
Indicates that two venues are related as peers or counterparts, typically sharing ownership, branding, or affiliation without one being subordinate to the other.
- F. None of above.
Provenance (4 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36c1b6c6748190b435c42c4e4c3ebc |
completed | June 20, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.