Triple
T23715917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollow |
E586001
|
entity |
| Predicate | firstRadioAirplayDate |
P62480
|
FINISHED |
| Object | 2013-01-08 |
—
|
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: 2013-01-08 | Statement: [Hollow, firstRadioAirplayDate, 2013-01-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRadioAirplayDate Context triple: [Hollow, firstRadioAirplayDate, 2013-01-08]
-
A.
firstAiredOnRadioStation
Indicates that a broadcast (such as a show, episode, or program) had its initial airing on a specified radio station.
-
B.
firstRadioBroadcastDate
chosen
Indicates the date on which an entity’s first radio broadcast took place.
-
C.
radioReleaseDate
Indicates the date on which something (typically a song, program, or broadcast content) was first released or made available on radio.
-
D.
firstTelecastOn
Indicates the date or event on which something, typically a program or broadcast, was first shown on television.
-
E.
firstBroadcastEndDate
Indicates the date on which the initial broadcast of something (such as a program or event) concluded.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77ab1bc8190be72606d363a07a0 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:54 p.m.