Triple

T15659939
Position Surface form Disambiguated ID Type / Status
Subject Nisa E376541 entity
Predicate locatedIn P40 FINISHED
Object Ahal Region E309109 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: Ahal Region | Statement: [Nisa, locatedIn, Ahal Region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ahal Region
Context triple: [Nisa, locatedIn, Ahal Region]
  • A. Ahal Region chosen
    Ahal Region is an administrative province in south-central Turkmenistan that surrounds the capital city, Ashgabat.
  • B. Razih region
    The Razih region is a mountainous area in northwestern Yemen known for its distinct local culture and dialects, including Razihi Arabic.
  • C. Bahdinan region
    The Bahdinan region is a historical and cultural area in northern Iraqi Kurdistan traditionally associated with the Behdini-speaking Kurds.
  • D. Lebap Region
    Lebap Region is an administrative province in eastern Turkmenistan known for its major city Turkmenabat and its location along the Amu Darya River.
  • E. Nimruz Province
    Nimruz Province is a sparsely populated, largely desert region in southwestern Afghanistan bordering Iran and Pakistan, known for its strategic location along key trade and smuggling routes.
  • 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_69d85cd1564c8190991adda63bfab4b0 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ef4e6a08190ad8bbafaa3612f22 completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff679e0f2c8190bbcb7051c38e1580 completed May 9, 2026, 4:58 p.m.
Created at: April 10, 2026, 4:15 a.m.