Triple
T21594184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Home Alabama |
E532854
|
entity |
| Predicate | frequentRadioFormat |
P9706
|
FINISHED |
| Object | classic rock radio |
—
|
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: classic rock radio | Statement: [Sweet Home Alabama, frequentRadioFormat, classic rock radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentRadioFormat Context triple: [Sweet Home Alabama, frequentRadioFormat, classic rock radio]
-
A.
radioFormat
chosen
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
B.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
C.
broadcastsInFormat
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
-
D.
broadcastFrequencyType
Indicates the type or category of frequency used for broadcasting a signal or transmission.
-
E.
hasRadioBroadcasts
Indicates that one entity transmits or provides content via radio broadcasts to another entity or audience.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefadf6e608190b42b26ea22c76ec6 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.