Triple

T32603535
Position Surface form Disambiguated ID Type / Status
Subject Itunyoso E833442 entity
Predicate recognizedAsIndigenousRegion P190371 FINISHED
Object true 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: true | Statement: [Itunyoso, recognizedAsIndigenousRegion, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognizedAsIndigenousRegion
Context triple: [Itunyoso, recognizedAsIndigenousRegion, true]
  • A. recognizedAsIndigenousIn
    Indicates that an entity is officially acknowledged or classified as Indigenous within a specified region, country, or jurisdiction.
  • B. recognizedAsIndigenousPeopleBy
    Indicates that one party formally acknowledges and accepts another party as belonging to an indigenous people or community.
  • C. indigenousTerritoryOf
    Indicates that a geographic area is traditionally inhabited, used, or claimed by a particular Indigenous people or community as their ancestral territory.
  • D. tribalRegionOf
    Indicates that one entity is the geographic region traditionally inhabited, controlled, or associated with a particular tribe.
  • E. hasIndigenousLanguageRegion
    Indicates that a region is associated with, or characterized by, the presence or use of one or more indigenous languages.
  • 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_69f3492ab63c8190aec24d5003b47c29 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fcc4b700748190ae00b21d09c96695 completed May 7, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69fcb0f9d3d881908a049475182fb039 completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc4b5f22c8190b8b256adbdc2570c completed May 7, 2026, 4:58 p.m.
Created at: May 1, 2026, 1:05 a.m.