Triple
T33593431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Deutschland |
E860491
|
entity |
| Predicate | offersPackage |
P43695
|
FINISHED |
| Object | sports subscription packages |
—
|
LITERAL 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: sports subscription packages | Statement: [Sky Deutschland, offersPackage, sports subscription packages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersPackage Context triple: [Sky Deutschland, offersPackage, sports subscription packages]
-
A.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
B.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
C.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
D.
offersMass
Indicates that one entity provides or makes available a certain mass or quantity of material or substance to another entity.
-
E.
offeredBundle
chosen
Indicates that one entity has presented a specific combination of items or services together as a bundled offer to another entity.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 1, 2026, 1:40 a.m.