Triple

T20593855
Position Surface form Disambiguated ID Type / Status
Subject Victoria, Chile E505998 entity
Predicate hasRegionalGovernmentLevel P1085 FINISHED
Object region 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: region | Statement: [Victoria, Chile, hasRegionalGovernmentLevel, region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegionalGovernmentLevel
Context triple: [Victoria, Chile, hasRegionalGovernmentLevel, region]
  • A. hasRegionalGovernmentAbove
    Indicates that one governmental unit is hierarchically subordinate to, and governed or overseen by, a higher-level regional government.
  • B. levelOfGovernment chosen
    Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
  • C. hasLocalGovernmentTier
    Indicates that one administrative unit is organized or governed at a specific level within a multi-tier local government structure.
  • D. hasRegionalGovernor
    Indicates that a region is administered or overseen by a specific governor responsible for its governance.
  • E. hasFormOfTerritorialOrganization
    Indicates that one entity possesses or is structured according to a particular type or form of territorial organization.
  • 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_69e0b4ba6ae88190af871e1f9522c704 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a97e3a7c8190b0b4604aaf40564b completed April 20, 2026, 10:32 p.m.
PD Predicate disambiguation batch_69e59fffe1748190825e4eaa90340631 completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:40 a.m.