Triple

T5829434
Position Surface form Disambiguated ID Type / Status
Subject Changana E129307 entity
Predicate glottologName P6521 FINISHED
Object Changana E129307 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: Changana | Statement: [Changana, glottologName, Changana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Changana
Context triple: [Changana, glottologName, Changana]
  • A. Changana chosen
    Changana is a Bantu language spoken primarily in southern Mozambique and neighboring regions, known for its significant influence on local varieties of African Portuguese.
  • B. Chanda
    Chanda was a historical kingdom associated with the Gond people, an indigenous community of central India.
  • C. Yanaon
    Yanaon is the former name of Yanam, a small coastal town in India that was once part of French India and retains a distinct Franco-Indian cultural heritage.
  • D. Machang
    Machang is a town and administrative district in the Malaysian state of Kelantan, known for its semi-urban character and role as a local commercial and educational hub.
  • E. Cailungo
    Cailungo is a locality within the municipality of Serravalle in the Republic of San Marino.
  • 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_69c00849d55481908b4f9f5543e0bf6d completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0346905848190a8f541401da05604 completed March 22, 2026, 6:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c09866fd248190b4248a993051b732 completed March 23, 2026, 1:33 a.m.
Created at: March 22, 2026, 3:54 p.m.