Triple
T6047995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Cubs |
E134714
|
entity |
| Predicate | hasBroadcastsOnTelevision |
P6989
|
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: [Iowa Cubs, hasBroadcastsOnTelevision, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastsOnTelevision Context triple: [Iowa Cubs, hasBroadcastsOnTelevision, yes]
-
A.
isTelevised
chosen
Indicates that an event, program, or activity is broadcast on television for public viewing.
-
B.
hasBroadcastCoverageIn
Indicates that a broadcast (such as a TV or radio program, channel, or signal) is available or transmitted within a specified geographic area or region.
-
C.
hasRadioBroadcasts
Indicates that one entity transmits or provides content via radio broadcasts to another entity or audience.
-
D.
usedForTelevisionBroadcastSchedules
Indicates that something is utilized to organize, present, or manage the timing and content of television broadcast schedules.
-
E.
hasBroadcastContent
Indicates that one entity (typically a broadcast or channel) carries, includes, or transmits the specified content.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056f387cc8190920b846995761aec |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.