Triple
T29941015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech Television |
E760497
|
entity |
| Predicate | childrenChannel |
P168794
|
FINISHED |
| Object | ČT :D |
—
|
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 :D | Statement: [Czech Television, childrenChannel, ČT :D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childrenChannel Context triple: [Czech Television, childrenChannel, ČT :D]
-
A.
childIn
Indicates that one entity is the offspring or direct descendant of another entity.
-
B.
childrenReceive
Indicates that one or more children are the recipients of something (such as an item, benefit, or message) from another source.
-
C.
childIs
Indicates that one entity is the child (offspring or subordinate descendant) of another entity.
-
D.
childDuring
Indicates that one entity is the child of another specifically during a given time interval or temporal context.
-
E.
childCustom
Indicates that an entity is a child in a custom-defined parent–child relationship specific to a particular context or schema.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678066d24819099ae7947cfb58743 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 6:22 p.m.