Triple

T4607753
Position Surface form Disambiguated ID Type / Status
Subject Himyar E100478 entity
Predicate neighbor P350 FINISHED
Object Qataban E236108 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: Qataban | Statement: [Himyar, neighbor, Qataban]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qataban
Context triple: [Himyar, neighbor, Qataban]
  • A. Qataban chosen
    Qataban was an ancient South Arabian kingdom known for its incense trade and strategic position along key caravan routes in what is now Yemen.
  • B. Qaʾan
    Qaʾan is a Mongol imperial title signifying the supreme ruler of the Mongol Empire, comparable to the Great Khan.
  • C. Kuqa
    Kuqa is an ancient oasis city in China’s Xinjiang region that historically served as a key Buddhist and Silk Road cultural center in the Tarim Basin.
  • D. Jabriya
    Jabriya is a residential suburb in Kuwait known for its mix of apartment buildings, schools, and local shops within the Hawalli Governorate.
  • E. Beruwala
    Beruwala is a coastal town in southwestern Sri Lanka known for its beaches, fishing harbor, and historic Muslim community.
  • 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_69bd43cce1e08190a07d53af6a9b6c24 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd599debdc81909d11d0e871c666bb completed March 20, 2026, 2:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfa725c048190af9eea074197fa32 completed March 21, 2026, 1:54 a.m.
Created at: March 20, 2026, 1:12 p.m.