Triple
T6666206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB Network Radio |
E151609
|
entity |
| Predicate | providesCoverageOf |
P42076
|
FINISHED |
| Object | MLB regular season |
—
|
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: MLB regular season | Statement: [MLB Network Radio, providesCoverageOf, MLB regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesCoverageOf Context triple: [MLB Network Radio, providesCoverageOf, MLB regular season]
-
A.
providesCoverage
chosen
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
B.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
C.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
D.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
E.
alsoCovers
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.