Triple

T4314997
Position Surface form Disambiguated ID Type / Status
Subject Al-Mansur E94166 entity
Predicate birthPlace P1 FINISHED
Object al-Humayma E362159 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: al-Humayma | Statement: [Al-Mansur, birthPlace, al-Humayma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: al-Humayma
Context triple: [Al-Mansur, birthPlace, al-Humayma]
  • A. al-Humayma chosen
    al-Humayma is an ancient settlement in southern Jordan that served as a key Abbasid family stronghold and early Islamic-era community along important trade routes.
  • B. Tabuk
    Tabuk is a city in northwestern Saudi Arabia known as the capital of the Tabuk Region and a growing hub for trade and development projects.
  • C. At-Turaif
    At-Turaif is a historic district in Diriyah, Saudi Arabia, renowned as the original home of the Saudi royal family and a UNESCO World Heritage Site.
  • D. Al-Kharj
    Al-Kharj is a city in central Saudi Arabia, southeast of Riyadh, known for its agricultural production and growing urban development.
  • E. Al-Uqair
    Al-Uqair is an ancient coastal port in eastern Saudi Arabia that historically served as a key trading and administrative gateway for the 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_69b3451886588190a3dd1305ea7c58dc completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b350f4448481908be2c7df9cc71bb9 completed March 12, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5d08245408190b1ce584c636bf168 completed March 14, 2026, 9:17 p.m.
Created at: March 12, 2026, 11:12 p.m.