Triple

T10490135
Position Surface form Disambiguated ID Type / Status
Subject Amdang language E247394 entity
Predicate hasGlottologName P6521 FINISHED
Object Amdang E869037 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: Amdang | Statement: [Amdang language, hasGlottologName, Amdang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amdang
Context triple: [Amdang language, hasGlottologName, Amdang]
  • A. Amdang chosen
    Amdang is an ethnic group primarily found in eastern Chad and western Sudan, known for speaking the Amdang (Biltine) language, a member of the Nilo-Saharan family.
  • B. Taebong
    Taebong was a short-lived Korean kingdom of the early 10th century that emerged during the Later Three Kingdoms period before being absorbed by Goryeo.
  • C. Nakchhong
    Nakchhong is a traditional ritual specialist and religious officiant within the Kirat Mundhum indigenous belief system.
  • D. Daegok-ri
    Daegok-ri is a locality in Ulsan, South Korea, best known as the site of the prehistoric Bangudae Petroglyphs.
  • E. Miryang
    Miryang is a city in South Gyeongsang Province, South Korea, known for its scenic river valley setting, historical sites, and role as a regional transport and educational hub.
  • 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_69d381c309b88190af78aa681cf6a4c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d5097d61e08190952d4354ef1bce52 completed April 7, 2026, 1:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69d94b0d05a88190be036a6e4ab374a7 completed April 10, 2026, 7:10 p.m.
Created at: April 6, 2026, 12:23 p.m.