Triple

T21477494
Position Surface form Disambiguated ID Type / Status
Subject Santo Cristo (Rio de Janeiro) E529898 entity
Predicate municipalRegionCode P31833 FINISHED
Object Região Administrativa I (Portuária) 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: Região Administrativa I (Portuária) | Statement: [Santo Cristo (Rio de Janeiro), municipalRegionCode, Região Administrativa I (Portuária)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalRegionCode
Context triple: [Santo Cristo (Rio de Janeiro), municipalRegionCode, Região Administrativa I (Portuária)]
  • A. municipalCodeSystem
    Indicates a system that defines, organizes, or standardizes codes or regulations used by a municipality.
  • B. districtCode
    Indicates that an entity is associated with, or identified by, a specific administrative district code.
  • C. subregionCodeFor chosen
    Indicates that one entity is the code assigned to identify a specific subregion of the other entity.
  • D. hasMunicipalityCode
    Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
  • E. cityCouncilRegion
    Indicates the administrative region or jurisdiction that a particular city council governs or represents.
  • 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_69e0c459acb481909bb6ee452a0045c7 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea1951fc8190910f634327aa5c3f completed April 23, 2026, 9:44 a.m.
PD Predicate disambiguation batch_69e631ec1d048190b6da97da8222e413 completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:20 p.m.