Triple

T9461069
Position Surface form Disambiguated ID Type / Status
Subject Proto-Eastern Iranian E228144 entity
Predicate hasDescendant P3654 FINISHED
Object Munji E230686 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: Munji | Statement: [Proto-Eastern Iranian, hasDescendant, Munji]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munji
Context triple: [Proto-Eastern Iranian, hasDescendant, Munji]
  • A. Munji chosen
    Munji is a lesser-known Eastern Iranian language spoken by the Munji people in the remote Munjan Valley of northeastern Afghanistan.
  • B. Minyong
    Minyong is a subgroup of the Adi people, an indigenous community of Arunachal Pradesh in Northeast India known for its distinct language and cultural traditions.
  • C. Tanaeang
    Tanaeang is a village settlement located on the atoll of Tabiteuea in the island nation of Kiribati in the central Pacific Ocean.
  • D. Jemgum
    Jemgum is a small municipality in the East Frisian region of Lower Saxony in northwestern Germany, known for its rural landscape along the Ems River.
  • E. Sungsang
    Sungsang is a coastal village in South Sumatra, Indonesia, known as a fishing and port settlement near the mouth of the Musi River.
  • 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_69ca843b123881909b0e60028475d12d completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7fcaf610819092bcd3b871665aa5 completed April 1, 2026, 8:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69d14bf027b48190a73dca431632104c completed April 4, 2026, 5:35 p.m.
Created at: March 30, 2026, 7:52 p.m.