Triple
T29941014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech Television |
E760497
|
entity |
| Predicate | sportsChannel |
P113805
|
FINISHED |
| Object | ČT sport |
—
|
NE NERFINISHED |
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: ČT sport | Statement: [Czech Television, sportsChannel, ČT sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsChannel Context triple: [Czech Television, sportsChannel, ČT sport]
-
A.
sportsAndEntertainmentChannel
chosen
Indicates a channel whose primary content focuses on sports events and entertainment programming.
-
B.
sportsProgram
Indicates a relationship where an entity is a sports-related program, event, or broadcast organized or provided by another entity.
-
C.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
D.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
E.
sportsAttraction
Indicates a relationship where an entity serves as a venue, site, or draw specifically for sports-related activities or events.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 6:22 p.m.