Triple
T37942588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurna |
E946525
|
entity |
| Predicate | hasPlayingContext |
P196811
|
FINISHED |
| Object | outdoor celebrations |
—
|
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: outdoor celebrations | Statement: [Zurna, hasPlayingContext, outdoor celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayingContext Context triple: [Zurna, hasPlayingContext, outdoor celebrations]
-
A.
hasPlayingMethod
Indicates that there is a specific way, technique, or method by which something is played or performed.
-
B.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
C.
hasAlbumContext
Indicates that something is associated with, or occurs within the context of, a particular album.
-
D.
hasPlaySource
Indicates that something derives its performance, playback, or execution from a specified source.
-
E.
hasBroadcastContext
Indicates that a broadcast is associated with a particular contextual setting, such as circumstances, environment, or conditions under which it is transmitted or received.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: May 3, 2026, 4:20 p.m.