Triple
T30904171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Luyas |
E787247
|
entity |
| Predicate | hasSceneConnection |
P22079
|
FINISHED |
| Object | Montreal indie music 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: Montreal indie music scene | Statement: [The Luyas, hasSceneConnection, Montreal indie music scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSceneConnection Context triple: [The Luyas, hasSceneConnection, Montreal indie music scene]
-
A.
containsScene
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
B.
hasSceneLocation
Indicates that a scene or event takes place at, or is set in, a specific location.
-
C.
hasInfluenceFromScene
chosen
Indicates that something is affected, shaped, or guided by the characteristics or context of a particular scene.
-
D.
associatedWithKeyScene
Indicates that something is linked or connected to a specific key scene, typically as a relevant element, feature, or reference.
-
E.
isAssociatedWithLabelScene
Indicates that an entity is connected to or involved with a particular labeled scene or scene annotation.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 8:50 p.m.