Triple

T32531373
Position Surface form Disambiguated ID Type / Status
Subject Santo Domingo del Estado E831463 entity
Predicate usesLocalGovernmentForm P86873 FINISHED
Object usos y costumbres 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: usos y costumbres | Statement: [Santo Domingo del Estado, usesLocalGovernmentForm, usos y costumbres]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesLocalGovernmentForm
Context triple: [Santo Domingo del Estado, usesLocalGovernmentForm, usos y costumbres]
  • A. isLocalGovernment
    Indicates that an entity functions as a governing body with authority over a specific local or regional area within a larger political system.
  • B. usesMunicipalGovernmentAct
    Indicates that an entity operates under, applies, or is governed by the provisions of a Municipal Government Act.
  • C. hasLocalGovernmentBody
    Indicates that an entity is administered or overseen by a specific local government authority or governing body.
  • D. hasLocalSelfGovernment
    Indicates that an entity possesses its own local governing authority with decision-making powers over local affairs.
  • E. hasLocalGovernmentSystem chosen
    Indicates that an entity possesses or operates under a particular system or structure of local government.
  • 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_69f34924b1cc8190ad3aca0c0f012a7e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc5740fc81909774a4f65201a3ff completed May 3, 2026, 7:42 a.m.
Created at: May 1, 2026, 1:01 a.m.