Triple

T10499773
Position Surface form Disambiguated ID Type / Status
Subject Vodafone UK E247638 entity
Predicate hasRoamingService P23934 FINISHED
Object international roaming 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: international roaming | Statement: [Vodafone UK, hasRoamingService, international roaming]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRoamingService
Context triple: [Vodafone UK, hasRoamingService, international roaming]
  • A. supportsRoamingWith chosen
    Indicates that one entity enables or is compatible with another entity’s ability to operate or be accessed while roaming across different networks or locations.
  • B. hasCellService
    Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
  • C. hasCellularComponent
    Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
  • D. hasSatelliteTerminal
    Indicates that an entity is equipped with or connected to a satellite communication terminal.
  • E. servesAsHubForFlagCarrierOf
    Indicates that a location or facility functions as a primary hub for the national flag carrier airline of a given country or region.
  • 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_69d381c309b88190af78aa681cf6a4c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d5098ef57c8190a9803c2c1736d299 completed April 7, 2026, 1:41 p.m.
PD Predicate disambiguation batch_69d4fb8e24ac8190912c9f11b8bd3084 completed April 7, 2026, 12:41 p.m.
Created at: April 6, 2026, 12:25 p.m.