Triple
T3121734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Alternative Songs chart |
E65199
|
entity |
| Predicate | genreTracked |
P33180
|
FINISHED |
| Object | alternative rock |
—
|
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: alternative rock | Statement: [US Alternative Songs chart, genreTracked, alternative rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreTracked Context triple: [US Alternative Songs chart, genreTracked, alternative rock]
-
A.
genreRecognized
Indicates that a particular genre has been identified or acknowledged as applicable to an entity.
-
B.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
-
C.
styleOfMusic
chosen
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
D.
genreContext
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
-
E.
genreRestriction
Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52ab05c819088204bbb608c837c |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.