Triple

T9269182
Position Surface form Disambiguated ID Type / Status
Subject Tangale E222778 entity
Predicate hasAlternativeName P39 FINISHED
Object Tangal E222778 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: Tangal | Statement: [Tangale, hasAlternativeName, Tangal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tangal
Context triple: [Tangale, hasAlternativeName, Tangal]
  • A. Tangtse
    Tangtse is a village in the Leh district of Ladakh, India, situated along key routes between the Indus Valley and the Pangong Tso region in the Himalayas.
  • B. Tangale chosen
    Tangale is a West Chadic language spoken primarily in Gombe State, northeastern Nigeria, by the Tangale people.
  • C. Tantamani
    Tantamani was a Kushite king of the 25th Dynasty of Egypt, known for his brief attempt to restore Nubian control over Egypt before being driven back by the Assyrians.
  • D. Tilantongo
    Tilantongo was a prominent pre-Columbian Mixtec city-state in present-day Oaxaca, Mexico, known as a political and cultural hub of the Mixtec civilization.
  • E. Rangloi
    Rangloi is a regional dialect of the Kumaoni language spoken in parts of the Indian Himalayan region.
  • 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_69ca841ffe208190aa7bcffbef2f8379 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd074ef7408190b213c09491918132 completed April 1, 2026, 11:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0c743c76c8190b39cfe25c6ab1db2 completed April 4, 2026, 8:09 a.m.
Created at: March 30, 2026, 7:33 p.m.