Triple

T18747190
Position Surface form Disambiguated ID Type / Status
Subject Homerite Kingdom E458433 entity
Predicate neighbor P350 FINISHED
Object Qataban NE NERFINISHED

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: [Homerite Kingdom, neighbor, Qataban]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qataban
Context triple: [Homerite Kingdom, 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. Qahhor
    Qahhor is a masculine given name commonly used in Central Asia, particularly in Tajik and Uzbek cultures.
  • C. Qaʾan
    Qaʾan is a Mongol imperial title signifying the supreme ruler of the Mongol Empire, comparable to the Great Khan.
  • D. Qanjobal
    Qanjobal is a Mayan language spoken primarily by the Qʼanjobʼal people in the highlands of Guatemala.
  • E. Hegh'bat
    Hegh'bat is a Klingon ritual of honorable suicide performed when a warrior becomes too old, weak, or disabled to live with dignity.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d394dc308190b6725073f5db324c completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e576936cf08190b3c0d2f4e8a616fc completed April 20, 2026, 12:42 a.m.
Created at: April 10, 2026, 11:51 a.m.