Triple
T37367632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish television industry |
E927754
|
entity |
| Predicate | keyChannel |
P184217
|
FINISHED |
| Object | SVT1 |
—
|
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: SVT1 | Statement: [Swedish television industry, keyChannel, SVT1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyChannel Context triple: [Swedish television industry, keyChannel, SVT1]
-
A.
keyLine
Indicates that a line or segment serves as a primary or defining reference line within a structure, system, or representation.
-
B.
coreChannel
chosen
Indicates a primary or central communication channel through which key information, signals, or interactions are transmitted.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keyPhase
Indicates that an event, action, or state occurs during a critical or defining phase within a larger process or sequence.
-
E.
keyChicane
Indicates a relationship where something functions as a primary or defining chicane (a key turning or zigzag feature) within a larger structure, path, or system.
- 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_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. |
Created at: May 3, 2026, 4:16 p.m.