Triple

T11939045
Position Surface form Disambiguated ID Type / Status
Subject Apsáalooke E284126 entity
Predicate language P15 FINISHED
Object Crow language E279197 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: Crow language | Statement: [Apsáalooke, language, Crow language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Crow language
Context triple: [Apsáalooke, language, Crow language]
  • A. Crow language chosen
    Crow language is a Native American Siouan language traditionally spoken by the Crow people of the north-central United States, particularly in Montana.
  • B. Fox language
    Fox language is a Native American Algonquian language traditionally spoken by the Meskwaki (Fox), Sauk, and Kickapoo peoples of the central United States.
  • C. Fur language
    The Fur language is an Eastern Sudanic language spoken primarily by the Fur people of western Sudan, especially in the Darfur region.
  • D. Nancowry language
    Nancowry language is an Austroasiatic language spoken by the Nicobarese people on Nancowry and nearby islands in India’s Nicobar archipelago.
  • E. Bru language
    Bru language is a Mon–Khmer language spoken by the Bru people across parts of Laos, Vietnam, and Thailand.
  • 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_69d6ab2ce9c48190b5d39511b524f666 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903415d2481909d84e6727454b9fe completed April 10, 2026, 2:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4409a40dc81909d87c50601b98b78 completed May 1, 2026, 5:56 a.m.
Created at: April 8, 2026, 9:45 p.m.