Triple

T1634210
Position Surface form Disambiguated ID Type / Status
Subject Google Cloud E35325 entity
Predicate hasGlobalInfrastructure P30769 FINISHED
Object data centers in multiple regions worldwide 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: data centers in multiple regions worldwide | Statement: [Google Cloud, hasGlobalInfrastructure, data centers in multiple regions worldwide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGlobalInfrastructure
Context triple: [Google Cloud, hasGlobalInfrastructure, data centers in multiple regions worldwide]
  • A. hasInfrastructureType
    Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
  • B. usesInfrastructure
    Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
  • C. hasInfrastructureOwner
    Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
  • D. hasGlobalReach
    Indicates that an entity’s influence, operations, or impact extends across multiple countries or worldwide.
  • E. hasGlobalPlan
    Indicates that an entity possesses or is associated with an overarching, comprehensive plan that applies at a global or system-wide level.
  • F. None of above. chosen

Provenance (4 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_69a886036bc081909ff5de16dbe5e8ea completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a96083e7308190abbf025fe8e43abb completed March 5, 2026, 10:52 a.m.
PD Predicate disambiguation batch_69a907cac610819083cafd4396b6d66c completed March 5, 2026, 4:34 a.m.
PDg Predicate description generation batch_69a9607716b4819092187f8c08daaf31 completed March 5, 2026, 10:52 a.m.
Created at: March 4, 2026, 7:28 p.m.