Triple

T38208658
Position Surface form Disambiguated ID Type / Status
Subject Next Alt E1009275 entity
Predicate controlsVotingRightsIn P8001 FINISHED
Object Altice group companies 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: Altice group companies | Statement: [Next Alt, controlsVotingRightsIn, Altice group companies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controlsVotingRightsIn
Context triple: [Next Alt, controlsVotingRightsIn, Altice group companies]
  • A. votingControl chosen
    Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
  • B. positionOnVotingRights
    Indicates a stance or viewpoint that an entity holds regarding policies or issues related to voting rights.
  • C. hasVotingPower
    Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
  • D. hasElectoralRight
    Indicates that an entity possesses the legal right to participate in elections, typically by voting or standing as a candidate.
  • E. hasDifferentVotingRightsFrom
    Indicates that two entities possess voting rights that are not identical in terms of scope, weight, or conditions.
  • 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_69f76dc94fcc8190bd2f55e81f9d6527 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff63225b6481909217ad11b4f7d3ba completed May 9, 2026, 4:38 p.m.
PD Predicate disambiguation batch_69ff60e0882c819085d097010db43ee0 completed May 9, 2026, 4:29 p.m.
Created at: May 3, 2026, 4:30 p.m.