Triple
T16651723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Mountain Sound Studios |
E404618
|
entity |
| Predicate | cityMusicScene |
P56238
|
FINISHED |
| Object | Vancouver rock scene |
—
|
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: Vancouver rock scene | Statement: [Little Mountain Sound Studios, cityMusicScene, Vancouver rock scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityMusicScene Context triple: [Little Mountain Sound Studios, cityMusicScene, Vancouver rock scene]
-
A.
culturalScene
Indicates a relationship where an entity is associated with, participates in, or characterizes a particular cultural environment, milieu, or set of cultural activities.
-
B.
musicalScene
Indicates a relationship where a scene in a work prominently features musical performance or music-driven action.
-
C.
cityCenterStage
Indicates that an event, activity, or focus is taking place prominently in the central area of a city.
-
D.
associatedWithMusicScene
chosen
Indicates a relationship where an entity is connected or linked to a particular music scene, culture, or community.
-
E.
metOperaCity
Indicates that an entity is the city in which the Metropolitan Opera is located or based.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf7ae7c81908b6807acd8f1669b |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.