Triple
T17862271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Cassidy |
E446101
|
entity |
| Predicate | radioWork |
P38565
|
FINISHED |
| Object | radio announcer in Dallas, Texas |
—
|
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: radio announcer in Dallas, Texas | Statement: [Ted Cassidy, radioWork, radio announcer in Dallas, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioWork Context triple: [Ted Cassidy, radioWork, radio announcer in Dallas, Texas]
-
A.
radioEmission
Indicates that one entity emits or produces radio-frequency radiation detectable as radio waves.
-
B.
radioAnnouncers
chosen
Indicates that one entity serves as a radio announcer for, or in association with, another entity.
-
C.
radioSystem
Indicates that one entity functions as, or is equipped with, a radio communication system used for transmitting and/or receiving signals.
-
D.
radioOperator
Indicates a relationship where one entity serves as the radio operator for another, handling radio communication duties on its behalf.
-
E.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49790ea148190b7a966812d44f430 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.