Triple
T35323601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stretch Music |
E1020115
|
entity |
| Predicate | hasSubgenreConcept |
P21666
|
FINISHED |
| Object | stretch music concept |
—
|
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: stretch music concept | Statement: [Stretch Music, hasSubgenreConcept, stretch music concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubgenreConcept Context triple: [Stretch Music, hasSubgenreConcept, stretch music concept]
-
A.
hasSubgenreRole
Indicates that an entity plays a specific role or function within a particular subgenre of a broader category.
-
B.
isAssociatedWithSubgenre
Indicates that one entity has a connection or linkage to a specific subgenre of a broader category.
-
C.
hasNotableSubgenre
Indicates that one genre is recognized as a particularly significant or prominent subgenre of another genre.
-
D.
hasSubConcept
chosen
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
E.
subgenre
Indicates that one genre is a more specific, subordinate category within a broader parent 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 3, 2026, 4:03 p.m.