Triple
T18500238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSR |
E452046
|
entity |
| Predicate | hasTelevisionService |
P124664
|
FINISHED |
| Object | Swiss public television |
—
|
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: Swiss public television | Statement: [SSR, hasTelevisionService, Swiss public television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTelevisionService Context triple: [SSR, hasTelevisionService, Swiss public television]
-
A.
televisionServiceStatus
Indicates the operational or subscription state of a television service for an entity.
-
B.
televisionServiceType
Indicates the specific kind or category of television service provided or used in the relationship.
-
C.
supportsStreamingServices
Indicates that one entity provides compatibility or functionality enabling the use of streaming services for another entity.
-
D.
hasTelevisionUsage
chosen
Indicates that an entity makes use of, accesses, or is associated with the use of a television.
-
E.
hasNightTubeServiceOn
Indicates that a transport service operates Night Tube (overnight) service on the specified day or line.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c3810c81908fa329c177c6d96c |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.