Triple
T15777096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakuvian |
E382517
|
entity |
| Predicate | associatedWithCulturalActivity |
P120283
|
FINISHED |
| Object | mugham music |
—
|
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: mugham music | Statement: [Bakuvian, associatedWithCulturalActivity, mugham music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCulturalActivity Context triple: [Bakuvian, associatedWithCulturalActivity, mugham music]
-
A.
hasCulturalEventLink
Indicates a relationship where an entity is associated with a link or reference to a related cultural event.
-
B.
hasCulturalOrganization
Indicates that an entity possesses, is associated with, or hosts a cultural organization (such as a museum, arts group, or cultural institution).
-
C.
cultActivity
Indicates involvement in, organization of, or association with the practices, rituals, or operations of a cult.
-
D.
hasCulturalEvent
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
E.
hasCulturalCommunity
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
- F. None of above. chosen
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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05199cd8881909462462cec34d35a |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.