Triple

T25848941
Position Surface form Disambiguated ID Type / Status
Subject Kavalan people E651147 entity
Predicate recognizedAsIndigenousGroupIn P12872 FINISHED
Object Taiwan NE NERFINISHED

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: Taiwan | Statement: [Kavalan people, recognizedAsIndigenousGroupIn, Taiwan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognizedAsIndigenousGroupIn
Context triple: [Kavalan people, recognizedAsIndigenousGroupIn, Taiwan]
  • A. recognizedAsIndigenousIn chosen
    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. representsIndigenousGroup
    Indicates that one entity is an indigenous group associated with, or represented by, another entity.
  • D. recognizedTribalGroups
    Indicates that certain tribal groups are officially acknowledged or granted formal recognition by an authority or governing body.
  • E. broaderIndigenousGrouping
    Indicates that one indigenous group is a broader, more inclusive grouping that encompasses another, more specific indigenous group.
  • 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_69e7ab39035c8190be15c8aaee1bb858 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 22, 2026, 7:57 a.m.