Triple
T27005974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minor League Baseball games |
E680240
|
entity |
| Predicate | mayBeBroadcastOn |
P29061
|
FINISHED |
| Object | local television |
—
|
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: local television | Statement: [Minor League Baseball games, mayBeBroadcastOn, local television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeBroadcastOn Context triple: [Minor League Baseball games, mayBeBroadcastOn, local television]
-
A.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
-
B.
intendedForBroadcast
Indicates that something is meant or designated to be transmitted to an audience via a broadcast medium.
-
C.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
D.
wasBroadcastOn
chosen
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
E.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 7 a.m.