Triple

T11220710
Position Surface form Disambiguated ID Type / Status
Subject Titin Valley E265552 entity
Predicate languageSpoken P151 FINISHED
Object Ashkun language E45083 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: Ashkun language | Statement: [Titin Valley, languageSpoken, Ashkun language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashkun language
Context triple: [Titin Valley, languageSpoken, Ashkun language]
  • A. Ashkun language chosen
    The Ashkun language is a Nuristani language spoken by the Ashkun people in remote regions of eastern Afghanistan.
  • B. Adasen language
    The Adasen language is an Austronesian language spoken by the Adasen people in the Cordillera region of northern Luzon in the Philippines.
  • C. Avikam language
    The Avikam language is a Kwa language spoken by the Avikam people of southern Côte d'Ivoire.
  • D. Avokaya language
    The Avokaya language is a Central Sudanic language spoken primarily by the Avokaya people in parts of South Sudan and the Democratic Republic of the Congo.
  • E. Asuri language
    Asuri language is an endangered Munda language of the Austroasiatic family spoken by the Asur tribal community in eastern India, primarily in Jharkhand.
  • 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_69d6aac59460819089b9848b27f57848 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8eb84c48190b4f3bede254afde2 completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4977cab4481909c6b94ca07cd5e4a completed April 19, 2026, 8:51 a.m.
Created at: April 8, 2026, 9:30 p.m.