Triple
T1459871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cal–Stanford Big Game |
E31485
|
entity |
| Predicate | hasTelevisionCoverage |
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: [Cal–Stanford Big Game, hasTelevisionCoverage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTelevisionCoverage Context triple: [Cal–Stanford Big Game, hasTelevisionCoverage, yes]
-
A.
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.
-
B.
hasPublisherCoverage
Indicates that a publisher provides content, services, or distribution that extend over or apply to a specified entity or area.
-
C.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
D.
isTelevised
chosen
Indicates that an event, program, or activity is broadcast on television for public viewing.
-
E.
notableEventCoverage
Indicates that there is media or documented coverage specifically focused on a notable event related to the subject.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.