Triple
T34008009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outlaws |
E872015
|
entity |
| Predicate | hasNotableSongFeature |
P203905
|
FINISHED |
| Object | extended guitar solos |
—
|
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: extended guitar solos | Statement: [Outlaws, hasNotableSongFeature, extended guitar solos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSongFeature Context triple: [Outlaws, hasNotableSongFeature, extended guitar solos]
-
A.
hasNotableSongType
Indicates that an entity is associated with a specific type or category of notable song.
-
B.
hasNotableSongWithBand
Indicates that an artist or individual is associated with a band through a song that is considered notable or significant.
-
C.
hasNotableSongNumber
Indicates that an entity is associated with a specific song identified by its notable number or index within a collection or sequence.
-
D.
hasNotableMusicWork
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
-
E.
hasNotableChartingSong
Indicates that an entity (typically a musical artist or group) has at least one song that has achieved notable placement on a recognized music chart.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_6a024936acc48190bc4a9abe4c519302 |
completed | May 11, 2026, 9:25 p.m. |
Created at: May 1, 2026, 1:50 a.m.