Triple

T34801912
Position Surface form Disambiguated ID Type / Status
Subject Optimum TV E1003238 entity
Predicate isBundledWith P103837 FINISHED
Object Optimum Internet 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: Optimum Internet | Statement: [Optimum TV, isBundledWith, Optimum Internet]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBundledWith
Context triple: [Optimum TV, isBundledWith, Optimum Internet]
  • A. bundledStatus
    Indicates that an item, service, or component is part of a bundle and specifies its inclusion state or condition within that bundle.
  • B. bundle chosen
    Indicates that multiple items are grouped or packaged together as a single combined unit or offering.
  • C. isAssociatedWithLineBundle
    Indicates that there exists a relationship linking an entity to a specific line bundle, typically signifying that the entity is defined, structured, or characterized in terms of that line bundle.
  • D. builtAsPartOf
    Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
  • E. isComponentAlongWith
    Indicates that an entity functions as a component in conjunction with one or more other components, typically forming a combined or complementary unit within a larger whole.
  • 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_69f76db543808190b188c6c86a91491b completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77a8adccc8190a80bb421f7a04e82 completed May 3, 2026, 4:40 p.m.
PD Predicate disambiguation batch_69f7795b1abc8190823664d1caa94649 completed May 3, 2026, 4:35 p.m.
Created at: May 3, 2026, 3:59 p.m.