Triple
T5870947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA on ABC broadcasts |
E130512
|
entity |
| Predicate | hasBroadcastRightsFor |
P60449
|
FINISHED |
| Object | regular season NBA games |
—
|
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: regular season NBA games | Statement: [NBA on ABC broadcasts, hasBroadcastRightsFor, regular season NBA games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastRightsFor Context triple: [NBA on ABC broadcasts, hasBroadcastRightsFor, regular season NBA games]
-
A.
hasBroadcastRightsHolder
Indicates that one entity holds the legal rights to broadcast content owned or controlled by another entity.
-
B.
hasBroadcastContent
chosen
Indicates that one entity (typically a broadcast or channel) carries, includes, or transmits the specified content.
-
C.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
D.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
E.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.