Triple
T5627041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Cubs radio broadcasts on WGN Radio |
E147742
|
entity |
| Predicate | signalReach |
P65505
|
FINISHED |
| Object | clear-channel station coverage at night |
—
|
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: clear-channel station coverage at night | Statement: [Chicago Cubs radio broadcasts on WGN Radio, signalReach, clear-channel station coverage at night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalReach Context triple: [Chicago Cubs radio broadcasts on WGN Radio, signalReach, clear-channel station coverage at night]
-
A.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
B.
signalLevel
Indicates the intensity or strength of a transmitted or received signal in a communication context.
-
C.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
D.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
-
E.
signaled
Indicates that one entity communicated a message, warning, or instruction to another through a deliberate signal or cue.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02237dd6081909f6a7d710b9cd651 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.