Triple
T15816521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daşoguz Region |
E383491
|
entity |
| Predicate | hasBorder |
P224
|
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: [Daşoguz Region, hasBorder, Ahal Region]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ahal Region Context triple: [Daşoguz Region, hasBorder, 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.
Tashauz Region
Tashauz Region was the former name of the Daşoguz administrative region in northern Turkmenistan, known for its location in the historical Khorezm area near the Uzbek border.
-
D.
Bahdinan region
The Bahdinan region is a historical and cultural area in northern Iraqi Kurdistan traditionally associated with the Behdini-speaking Kurds.
-
E.
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.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a306a48190840adc49df2c26c5 |
completed | April 16, 2026, 11:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa939b4608190ac411b2f2f61e19e |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.