Triple
T17440898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nestorio (municipality) |
E424646
|
entity |
| Predicate | RiverPartyGenre |
P33180
|
FINISHED |
| Object | music festival |
—
|
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: music festival | Statement: [Nestorio (municipality), RiverPartyGenre, music festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RiverPartyGenre Context triple: [Nestorio (municipality), RiverPartyGenre, music festival]
-
A.
styleOfMusic
chosen
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
B.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
C.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
D.
genreShift
Indicates a change in the type or style of content, such as switching from one genre to another within a work or between works.
-
E.
bearerGenre
Indicates that an entity (the bearer) is associated with or characterized by a particular 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ff75538819083f77756d39a1aaa |
completed | April 19, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.