Triple
T24022936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KROQ-FM |
E594872
|
entity |
| Predicate | hasPlaylistFocus |
P154904
|
FINISHED |
| Object | contemporary 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: contemporary rock | Statement: [KROQ-FM, hasPlaylistFocus, contemporary rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaylistFocus Context triple: [KROQ-FM, hasPlaylistFocus, contemporary rock]
-
A.
hasCollectionFocus
Indicates that something is primarily concerned with, centered on, or directed toward a particular collection or set of items.
-
B.
hasProgramFocus
Indicates that an entity (such as a program or initiative) is oriented around or primarily concerned with a particular thematic area, topic, or objective.
-
C.
hasGameFocus
Indicates that something is primarily concerned with, oriented toward, or centered around games or gaming activities.
-
D.
hasReplayabilityFocus
Indicates that something is designed or evaluated with an emphasis on being enjoyable or worthwhile to experience multiple times.
-
E.
hasFocusGroup
Indicates that an entity is associated with or participates in a specific focus group for targeted discussion, feedback, or research.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7680d5c81908d6a670159879236 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:52 p.m.