Triple

T3791578
Position Surface form Disambiguated ID Type / Status
Subject Pochutec E89660 entity
Predicate hasGlottologName P6521 FINISHED
Object Pochutec E89660 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: Pochutec | Statement: [Pochutec, hasGlottologName, Pochutec]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pochutec
Context triple: [Pochutec, hasGlottologName, Pochutec]
  • A. Pochutec chosen
    Pochutec is an extinct Uto-Aztecan language once spoken in the Pochutla region of Oaxaca, Mexico.
  • B. Chopok
    Chopok is a prominent mountain peak in central Slovakia’s Low Tatras range, popular for hiking, skiing, and panoramic alpine views.
  • C. Pucikwar
    Pucikwar is an extinct Great Andamanese language once spoken by the Pucikwar people of the Andaman Islands in India.
  • D. Chukchucha
    Chukchucha is a village-level settlement located on Car Nicobar Island in the Nicobar district of India’s Andaman and Nicobar Islands.
  • E. Pasochoa
    Pasochoa is an extinct volcanic mountain in Ecuador known for its lush cloud forests and rich biodiversity within a protected ecological reserve.
  • 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_69aed9597d6881909b6ee3b9de859223 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee7687c4481908d5e6988e2638b68 completed March 9, 2026, 3:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4f055e3988190a1b3633e390c0d6f completed March 14, 2026, 5:21 a.m.
Created at: March 9, 2026, 3:15 p.m.