Triple

T38097179
Position Surface form Disambiguated ID Type / Status
Subject Shinnecock E951275 entity
Predicate hasTribalNation P130006 FINISHED
Object Shinnecock Indian Nation 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: Shinnecock Indian Nation | Statement: [Shinnecock, hasTribalNation, Shinnecock Indian Nation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTribalNation
Context triple: [Shinnecock, hasTribalNation, Shinnecock Indian Nation]
  • A. hasTribalPresence
    Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
  • B. hasTribalEntity chosen
    Indicates that one entity is associated with, belongs to, or is part of a specific tribal group or tribal organizational body.
  • C. hasTribalAssociation
    Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
  • D. hasTribalInstitution
    Indicates that an entity possesses, is associated with, or hosts a tribal institution (such as a tribal government, organization, or culturally recognized tribal body).
  • E. hasTribalAuthority
    Indicates that an entity holds recognized governing or decision-making power within a specific tribe or tribal community.
  • 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_69f76f04960c8190a83f14ae4c67f5bc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a005be4615c8190a710ab704a46c564 completed May 10, 2026, 10:20 a.m.
PD Predicate disambiguation batch_6a005b8b1cc08190850a392761b84e74 completed May 10, 2026, 10:18 a.m.
Created at: May 3, 2026, 4:21 p.m.