Triple
T37367640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish television industry |
E927754
|
entity |
| Predicate | keyStreamingService |
P187785
|
FINISHED |
| Object | SVT Play |
—
|
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: SVT Play | Statement: [Swedish television industry, keyStreamingService, SVT Play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyStreamingService Context triple: [Swedish television industry, keyStreamingService, SVT Play]
-
A.
keyHub
Indicates a central or primary element that connects, coordinates, or controls multiple related components or interactions.
-
B.
keySystem
Indicates a relationship where one entity functions as the primary or controlling system that governs, secures, or coordinates access to another entity or set of entities.
-
C.
keyClient
Indicates that one entity is a primary or strategically important client of another entity.
-
D.
keyStar
Indicates that one entity serves as a primary or central key reference in relation to another entity.
-
E.
keyCenter
Indicates the central or primary tonal focus around which other related elements are organized or interpreted.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.