Triple
T11956387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petronio Álvarez Pacific Music Festival |
E284563
|
entity |
| Predicate | genreFeatured |
P21380
|
FINISHED |
| Object | currulao |
—
|
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: currulao | Statement: [Petronio Álvarez Pacific Music Festival, genreFeatured, currulao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreFeatured Context triple: [Petronio Álvarez Pacific Music Festival, genreFeatured, currulao]
-
A.
genreFeatures
Indicates that a particular genre is characterized or defined by certain features or attributes.
-
B.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
C.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
D.
genreSpecialty
chosen
Indicates that an entity specializes in or is particularly associated with a specific genre.
-
E.
genreDiversity
Indicates the extent to which an entity involves, includes, or spans multiple distinct genres rather than being confined to a single genre.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.