Triple
T33088076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virtuoso No. 3 |
E846697
|
entity |
| Predicate | hasPrimarySubgenre |
P203319
|
FINISHED |
| Object | bebop-influenced jazz guitar |
—
|
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: bebop-influenced jazz guitar | Statement: [Virtuoso No. 3, hasPrimarySubgenre, bebop-influenced jazz guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySubgenre Context triple: [Virtuoso No. 3, hasPrimarySubgenre, bebop-influenced jazz guitar]
-
A.
hasNotableSubgenre
Indicates that one genre is recognized as a particularly significant or prominent subgenre of another genre.
-
B.
hasSubgenreRole
Indicates that an entity plays a specific role or function within a particular subgenre of a broader category.
-
C.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
D.
isAssociatedWithSubgenre
Indicates that one entity has a connection or linkage to a specific subgenre of a broader category.
-
E.
secondaryGenre
Indicates that an entity (such as a work or item) has an additional, non-primary genre classification associated with it.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0154b16a3c8190b808a460ae3a91ac |
completed | May 11, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a01539f19d88190b2de63f5262b1074 |
completed | May 11, 2026, 3:57 a.m. |
| PDg | Predicate description generation | batch_6a0154b0a9e48190ae747136b4587ceb |
completed | May 11, 2026, 4:01 a.m. |
Created at: May 1, 2026, 1:26 a.m.