Triple
T28344988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Worldwide |
E717924
|
entity |
| Predicate | handledRightsFor |
P39434
|
FINISHED |
| Object | BBC television programmes |
—
|
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: BBC television programmes | Statement: [BBC Worldwide, handledRightsFor, BBC television programmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledRightsFor Context triple: [BBC Worldwide, handledRightsFor, BBC television programmes]
-
A.
hasRightsOver
chosen
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
B.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
-
C.
hasRightsSimilarTo
Indicates that one entity possesses rights that are comparable or equivalent in scope or nature to those held by another entity.
-
D.
acquiredRightsTo
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
E.
accessRight
Indicates that one entity has a specified permission or level of authorization to use, view, or interact with another entity or resource.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 12:42 a.m.