Triple
T14955524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBAI |
E372914
|
entity |
| Predicate | airdateOfNotableBroadcast |
P62879
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [WBAI, airdateOfNotableBroadcast, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airdateOfNotableBroadcast Context triple: [WBAI, airdateOfNotableBroadcast, 1973]
-
A.
notableBroadcast
Indicates that an entity is recognized for having made a significant or widely known broadcast.
-
B.
airdateDetail
chosen
Indicates the specific broadcast scheduling information for something, such as its original air date, time, or related airing details.
-
C.
specialEpisodeAirDate
Indicates the calendar date on which a special episode is broadcast or made available to the public.
-
D.
notableBroadcastFeature
Indicates that something has a distinctive or noteworthy characteristic related to its broadcast or transmission.
-
E.
notableEpisodeEvent
Indicates that an event is especially significant or noteworthy within the context of a particular episode.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cc73848190ac181782b20dc838 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.