Triple
T20797943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto in Slendro |
E511960
|
entity |
| Predicate | usesAesthetic |
P102534
|
FINISHED |
| Object | gamelan aesthetics |
—
|
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: gamelan aesthetics | Statement: [Concerto in Slendro, usesAesthetic, gamelan aesthetics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAesthetic Context triple: [Concerto in Slendro, usesAesthetic, gamelan aesthetics]
-
A.
associatedAesthetic
chosen
Indicates a relationship where one entity is linked to or characterized by a particular aesthetic style, quality, or visual/theme-based sensibility.
-
B.
aestheticRole
Indicates the role or function something has within an aesthetic or artistic context (e.g., as artwork, decoration, or design element).
-
C.
usesAsStyleOf
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
D.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
E.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2ae2c4c819087f620df31dc1aba |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.