Triple
T25851473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1904 World Series |
E651220
|
entity |
| Predicate | hadNewspaperCoverage |
P139736
|
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: [1904 World Series, hadNewspaperCoverage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNewspaperCoverage Context triple: [1904 World Series, hadNewspaperCoverage, yes]
-
A.
hasMediaCoverageSince
Indicates that an entity has had media coverage starting from a specified point in time and continuing from then onward.
-
B.
hasLocalMediaCoverageFrom
Indicates that an entity has been reported on or featured by a specified local media outlet or source.
-
C.
hasMediaCoverageLevel
Indicates the degree or extent to which something is covered or reported on by media outlets.
-
D.
hasMediaCoverageTopic
Indicates that a piece of media coverage is about, focused on, or thematically related to a particular topic.
-
E.
hasNotableMediaCoverage
chosen
Indicates that the subject has received significant attention or coverage in media outlets such as news, television, radio, or online publications.
- 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.