Triple
T15314753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arachosia |
E366125
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Gedrosia |
E1153743
|
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: Gedrosia | Statement: [Arachosia, borderedBy, Gedrosia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gedrosia Context triple: [Arachosia, borderedBy, Gedrosia]
-
A.
Arachosia
Arachosia was an ancient historical region in south-central Asia, roughly corresponding to parts of modern southern Afghanistan and Pakistan, known as a crossroads of Persian, Greek, and later empires.
-
B.
Tihama
Tihama is a hot, low-lying coastal plain along the Red Sea, primarily in western Yemen and southwestern Saudi Arabia.
-
C.
Kharas
Kharas is a Palestinian village located in the Hebron Governorate in the southern West Bank.
-
D.
Sogdia
Sogdia was an ancient Iranian-speaking region in Central Asia, renowned as a key hub of trade and culture along the Silk Road.
-
E.
Drangiana
chosen
Drangiana was an ancient historical region in southwestern Afghanistan and eastern Iran, known from Achaemenid and later classical sources.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd050108190a584543cb93943a4 |
completed | April 16, 2026, 1:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff133d171c8190918c9624bcdb7451 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:16 a.m.