Triple
T25851471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1904 World Series |
E651220
|
entity |
| Predicate | hadTelevisionCoverage |
P118394
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [1904 World Series, hadTelevisionCoverage, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadTelevisionCoverage Context triple: [1904 World Series, hadTelevisionCoverage, no]
-
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.
partialTelevisionCoverage
Indicates that the subject provides or receives television coverage that is limited in scope, duration, or geographic reach rather than full or comprehensive coverage.
-
C.
formerTelevisionCoverage
Indicates that an entity previously provided television coverage of another entity but no longer does so.
-
D.
hasMediaCoverageSince
Indicates that an entity has had media coverage starting from a specified point in time and continuing from then onward.
-
E.
tvCoverage
chosen
Indicates that an entity provides or is the subject of television broadcast coverage for another entity or event.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6023b96208190925872085ada10e3 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:58 a.m.