Triple

T28296619
Position Surface form Disambiguated ID Type / Status
Subject Azure China E713585 entity
Predicate networkSeparation P168100 FINISHED
Object physically isolated from global Azure network 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: physically isolated from global Azure network | Statement: [Azure China, networkSeparation, physically isolated from global Azure network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: networkSeparation
Context triple: [Azure China, networkSeparation, physically isolated from global Azure network]
  • A. networkDivision
    Indicates a relationship where a larger network is partitioned or segmented into smaller, distinct subnetworks or sections.
  • B. networkSection
    Indicates that one entity represents a specific section, segment, or subdivision within a larger network structure.
  • C. networkModel
    Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
  • D. networkScale
    Indicates the relative size, capacity, or extent of a network in terms of its reach or resources.
  • E. networkCenter
    Indicates that an entity functions as the central or primary hub within a network, coordinating or connecting other nodes.
  • 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_69efb524ab688190a1ce7ee7c9520932 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f673633d288190b52ceb9f8a057c44 completed May 2, 2026, 9:57 p.m.
PD Predicate disambiguation batch_69f66ec3d3d48190ab2f2b71939e572e completed May 2, 2026, 9:38 p.m.
PDg Predicate description generation batch_69f67256d064819094be04fc1bbbc635 completed May 2, 2026, 9:53 p.m.
Created at: April 27, 2026, 11:32 p.m.