Triple
T34215005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TV1 |
E877759
|
entity |
| Predicate | primaryChannelOf |
P55012
|
FINISHED |
| Object | Sveriges Television |
E51238
|
NE 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: Sveriges Television | Statement: [TV1, primaryChannelOf, Sveriges Television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryChannelOf Context triple: [TV1, primaryChannelOf, Sveriges Television]
-
A.
primaryChannel
Indicates that one channel is designated as the main or most important channel among a set of available channels.
-
B.
primaryFor
chosen
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primaryExchange
Indicates the main or most significant transfer or trade interaction occurring between two parties or systems.
-
D.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
-
E.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
- F. None of above.
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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a373606cbdc819082aa0b391887fde9 |
completed | June 21, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.