Triple
T2376945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB on TBS |
E46218
|
entity |
| Predicate | typeOfCoverage |
P38809
|
FINISHED |
| Object | national MLB coverage |
—
|
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: national MLB coverage | Statement: [MLB on TBS, typeOfCoverage, national MLB coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCoverage Context triple: [MLB on TBS, typeOfCoverage, national MLB coverage]
-
A.
typeOfDiscriminationCovered
Indicates that a particular kind or category of discriminatory behavior is included within the scope of protections, rules, or analysis.
-
B.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
C.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
D.
primaryCoverage
Indicates that one entity serves as the main or principal source of coverage (such as insurance or protection) for another entity.
-
E.
insuranceType
Indicates the specific category or kind of insurance coverage associated with an entity or relationship.
- F. None of above. chosen
Provenance (4 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abca4c937c8190b4dfca716b868d4f |
completed | March 7, 2026, 6:48 a.m. |
Created at: March 4, 2026, 7:57 p.m.