Triple
T17307161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sur tribe |
E420192
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Ghor |
E139113
|
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: Ghor | Statement: [Sur tribe, region, Ghor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ghor Context triple: [Sur tribe, region, Ghor]
-
A.
Ghor
Ghor is a low-lying, fertile region within the Jordan Rift Valley known for its agricultural lands and proximity to the Jordan River.
-
B.
Ghur
Ghur was a historical region in central Afghanistan that served as the mountainous heartland of the Ghurid dynasty.
-
C.
Ghor Province
chosen
Ghor Province is a mountainous, centrally located region of Afghanistan known for its remote terrain, historical significance, and ethnically diverse population.
-
D.
Khōwār
Khōwār is an Indo-Aryan language spoken primarily in Pakistan’s Chitral region and surrounding areas.
-
E.
Ghorband
Ghorband is a notable town in Afghanistan’s Parwan Province, known for its location in a fertile valley northwest of Kabul.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4390005dc81908345ebb6dd970582 |
completed | April 19, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c440c58819084792fcd6b7a7a79 |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 10, 2026, 5:43 a.m.