Triple
T7017895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taftan border crossing |
E162741
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Taftan |
E162739
|
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: Taftan | Statement: [Taftan border crossing, locatedIn, Taftan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taftan Context triple: [Taftan border crossing, locatedIn, Taftan]
-
A.
Taftan
chosen
Taftan is a town in Pakistan’s Balochistan province known as a key border crossing and trade gateway between Pakistan and Iran.
-
B.
Shastan
Shastan is a Native American language (or group of closely related languages) historically spoken by the Shasta people of northern California and southern Oregon.
-
C.
Hereti
Hereti was a historical region and principality in eastern Georgia, later often associated with Kakheti, known for its early Christian heritage and strategic location in the Caucasus.
-
D.
Šišan
Šišan is a village in Istria, Croatia, known as one of the traditional centers of the Istriot language and its cultural heritage.
-
E.
Yasna
Yasna is a central Zoroastrian liturgical ceremony and its associated collection of sacred texts, forming one of the core sections of the Avesta.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e1e79c108190a507335e9dbf2716 |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7884ac340819093e1812738d5e30f |
completed | March 28, 2026, 7:50 a.m. |
Created at: March 27, 2026, 2:34 p.m.