Triple
T33592233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kudos |
E860455
|
entity |
| Predicate | hasProducedForPlatform |
P39167
|
FINISHED |
| Object | BBC One |
E13555
|
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: BBC One | Statement: [Kudos, hasProducedForPlatform, BBC One]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProducedForPlatform Context triple: [Kudos, hasProducedForPlatform, BBC One]
-
A.
platformProduced
Indicates that a platform (such as a service, system, or medium) is responsible for creating, generating, or enabling the production of a particular entity or output.
-
B.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
C.
hadPlatforms
Indicates that something was equipped with or featured one or more platforms.
-
D.
platformsDevelopedFor
chosen
Indicates the platforms (e.g., operating systems, devices, or environments) for which something has been specifically created or adapted.
-
E.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01ac8b4ac881908aa52079c985ddac |
completed | May 11, 2026, 10:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35afec25a48190ac49d5d7128a1718 |
completed | June 19, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_6a01aa7fa7b48190b4911aa6bcabe7eb |
completed | May 11, 2026, 10:07 a.m. |
Created at: May 1, 2026, 1:40 a.m.