Triple
T814831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Through the Years |
E17628
|
entity |
| Predicate | radioFormatStaple |
P9706
|
FINISHED |
| Object | adult contemporary 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: adult contemporary radio | Statement: [Through the Years, radioFormatStaple, adult contemporary radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioFormatStaple Context triple: [Through the Years, radioFormatStaple, adult contemporary radio]
-
A.
radioFormat
chosen
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
B.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
-
C.
countryStationed
Indicates that an entity is assigned, based, or deployed within the territory of a specified country.
-
D.
sisterStation
Indicates that two broadcast stations are related as counterparts, typically serving different areas or platforms under common ownership or affiliation.
-
E.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5035608190bff5f3843b75e662 |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.