Triple

T23332959
Position Surface form Disambiguated ID Type / Status
Subject Data Retention and Investigatory Powers Act 2014 E591494 entity
Predicate affectedStakeholders P1553 FINISHED
Object telecommunications service providers 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: telecommunications service providers | Statement: [Data Retention and Investigatory Powers Act 2014, affectedStakeholders, telecommunications service providers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: affectedStakeholders
Context triple: [Data Retention and Investigatory Powers Act 2014, affectedStakeholders, telecommunications service providers]
  • A. affectedCompany
    Indicates that a company is impacted or influenced by a particular event, action, or entity.
  • B. affectedPeople
    Indicates the people who are impacted or influenced by a particular event, action, or condition.
  • C. affectedPerson
    Indicates that a particular person is impacted or influenced by an event, action, or condition.
  • D. hasStakeholder chosen
    Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
  • E. standAffected
    Indicates that an entity is in a state or position of being impacted or influenced by another entity or event.
  • 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_69e25d20156c81908c5c53195bd9c738 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f197eecc5c81908089eb43bc701196 completed April 29, 2026, 5:32 a.m.
PD Predicate disambiguation batch_69effcf8ca2c8190887d4f4656617d21 completed April 28, 2026, 12:19 a.m.
Created at: April 17, 2026, 5:15 p.m.