Triple
T28541560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KHL on ESPN |
E722303
|
entity |
| Predicate | subjectOfCoverage |
P133491
|
FINISHED |
| Object | professional ice hockey |
—
|
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: professional ice hockey | Statement: [KHL on ESPN, subjectOfCoverage, professional ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfCoverage Context triple: [KHL on ESPN, subjectOfCoverage, professional ice hockey]
-
A.
subjectOfClaim
Indicates that an entity is the topic, target, or focus of a particular claim or assertion made by another entity.
-
B.
categoryCovered
Indicates that one category is included within, addressed by, or encompassed under the scope of another entity or context.
-
C.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
D.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
E.
genreOfCoverage
chosen
Indicates the type or category of content that characterizes a particular coverage or media piece.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 3:35 a.m.