Triple

T117355
Position Surface form Disambiguated ID Type / Status
Subject Adirondack people E2369 entity
Predicate warning P2399 FINISHED
Object term may obscure distinct identities of Indigenous groups 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: term may obscure distinct identities of Indigenous groups | Statement: [Adirondack people, warning, term may obscure distinct identities of Indigenous groups]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: warning
Context triple: [Adirondack people, warning, term may obscure distinct identities of Indigenous groups]
  • A. threat
    Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
  • B. fault
    Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
  • C. warnsAbout chosen
    Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
  • D. issue
    Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
  • E. triggered
    Indicates that one entity causes an event, action, or process involving another entity to start or occur.
  • 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_69a2506c5428819085c28a8884790e29 completed Feb. 28, 2026, 2:18 a.m.
NER Named-entity recognition batch_69a257845c548190bfb49409988d1c57 completed Feb. 28, 2026, 2:48 a.m.
PD Predicate disambiguation batch_69a256456d908190b52c937fe6c4343f completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:24 a.m.