Triple

T13985473
Position Surface form Disambiguated ID Type / Status
Subject Ailuk (village) E336426 entity
Predicate hasGovernmentTypeAtLocalLevel P86873 FINISHED
Object local council 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: local council | Statement: [Ailuk (village), hasGovernmentTypeAtLocalLevel, local council]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGovernmentTypeAtLocalLevel
Context triple: [Ailuk (village), hasGovernmentTypeAtLocalLevel, local council]
  • A. levelOfGovernment
    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.
  • B. hasLocalGovernmentSystem chosen
    Indicates that an entity possesses or operates under a particular system or structure of local government.
  • C. hasLocalGovernmentBody
    Indicates that an entity is administered or overseen by a specific local government authority or governing body.
  • D. hasRegionalGovernmentAbove
    Indicates that one governmental unit is hierarchically subordinate to, and governed or overseen by, a higher-level regional government.
  • E. hasCityGovernmentType
    Indicates the specific form or structure of municipal governance that administers a city.
  • 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_69d81c639e808190a0e4b4f3d31c6a59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ea3e5a081908ed8ead108139252 completed April 14, 2026, 12:10 p.m.
PD Predicate disambiguation batch_69dd465a21408190b912a42c50ffa0d9 completed April 13, 2026, 7:39 p.m.
Created at: April 9, 2026, 10:18 p.m.