Triple
T5920078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haight-Ashbury |
E131677
|
entity |
| Predicate | hasMusicScene |
P56238
|
FINISHED |
| Object | psychedelic rock |
—
|
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: psychedelic rock | Statement: [Haight-Ashbury, hasMusicScene, psychedelic rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicScene Context triple: [Haight-Ashbury, hasMusicScene, psychedelic rock]
-
A.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
B.
associatedWithMusicScene
chosen
Indicates a relationship where an entity is connected or linked to a particular music scene, culture, or community.
-
C.
hasMusicInstitution
Indicates that an entity is associated with or hosts a music-related institution, such as a conservatory, music school, or similar organization.
-
D.
hasArtScene
Indicates that a place or community possesses an active or notable community of artistic activity, events, and institutions.
-
E.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.