Triple
T5166141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSPN (AM) |
E116561
|
entity |
| Predicate | broadcastsVia |
P17106
|
FINISHED |
| Object | radio frequency |
—
|
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 frequency | Statement: [KSPN (AM), broadcastsVia, radio frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastsVia Context triple: [KSPN (AM), broadcastsVia, radio frequency]
-
A.
broadcastsTo
Indicates that one entity transmits or disseminates information, signals, or content to another entity or group of entities.
-
B.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
C.
broadcastVia
chosen
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
-
D.
broadcastFrom
Indicates that some content, signal, or message is transmitted or emitted starting at a particular source location, device, or entity.
-
E.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd792af4648190934cf2db523f6921 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.