Triple

T3936132
Position Surface form Disambiguated ID Type / Status
Subject Pucikwar E90916 entity
Predicate relatedTo P37 FINISHED
Object Aka-Kol E382782 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: Aka-Kol | Statement: [Pucikwar, relatedTo, Aka-Kol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aka-Kol
Context triple: [Pucikwar, relatedTo, Aka-Kol]
  • A. Aka-Kol chosen
    Aka-Kol is an extinct Great Andamanese language once spoken by the indigenous Kol people of the Andaman Islands in India.
  • B. Pishpek
    Pishpek, now known as Bishkek, is the capital and largest city of Kyrgyzstan in Central Asia.
  • C. Yakut
    Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
  • D. Anadyr
    Anadyr is a remote Arctic port town in Russia’s Far East, situated on the Anadyr River near the Bering Sea and serving as the main administrative, economic, and cultural center of the surrounding region.
  • E. Tatitlek
    Tatitlek is a small Alaska Native village in south-central Alaska, traditionally inhabited by the Alutiiq people and known for its subsistence lifestyle and coastal setting.
  • 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_69aed95f26e0819094b0e71974543a19 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeedcd29148190a98e4549c9ed8888 completed March 9, 2026, 3:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5288eb3e481909a68531fd37371a4 completed March 14, 2026, 9:21 a.m.
Created at: March 9, 2026, 3:23 p.m.