Triple
T37053460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSL (AM) |
E917109
|
entity |
| Predicate | clearChannelStation |
P187280
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [KSL (AM), clearChannelStation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clearChannelStation Context triple: [KSL (AM), clearChannelStation, yes]
-
A.
clearChannelClass
Indicates that a communication or transport channel belongs to a class or category that is unobstructed, unoccupied, or otherwise available for use.
-
B.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
C.
claimedStation
Indicates that an entity has asserted ownership, control, or responsibility over a particular station.
-
D.
closedAsLinearChannel
Indicates that one entity has been closed or terminated by being converted into or treated as a linear (one-way, sequential) communication channel.
-
E.
linearChannel
Indicates a relationship where communication or flow occurs through a single, sequential path or medium, typically in one dimension or along a straight route.
- F. None of above. chosen
Provenance (4 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.