Triple

T15557180
Position Surface form Disambiguated ID Type / Status
Subject Lower Tanana E370899 entity
Predicate isPartOf P10 FINISHED
Object Tanana language E353075 NE 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: Tanana language | Statement: [Lower Tanana, isPartOf, Tanana language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tanana language
Context triple: [Lower Tanana, isPartOf, Tanana language]
  • A. Tanaina language
    Tanaina language is an Athabaskan language traditionally spoken by the Dena’ina people of south-central Alaska, particularly around Cook Inlet.
  • B. Lower Tanana language chosen
    The Lower Tanana language is an endangered Northern Athabaskan language traditionally spoken by the Tanana people in the interior region of Alaska.
  • C. Tsakhur language
    The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
  • D. Tanema language
    Tanema is a nearly extinct Oceanic language once spoken on Vanikoro Island in the Temotu Province of the Solomon Islands.
  • E. Denya language
    Denya is a Bantoid language of the Mamfe group spoken by a small community in southwestern Cameroon.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04a97dbfc8190a98cbbac5e71ba88 completed April 16, 2026, 2:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff456427988190bddea01f5cb159d9 completed May 9, 2026, 2:32 p.m.
Created at: April 10, 2026, 4:09 a.m.