Triple
T14099571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sistan |
E339343
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Sakastan |
E1024074
|
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: Sakastan | Statement: [Sistan, historicalName, Sakastan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sakastan Context triple: [Sistan, historicalName, Sakastan]
-
A.
Sakastan
chosen
Sakastan was an ancient historical region in what is now southeastern Iran and surrounding areas, known as a major center of Indo-Iranian and later Indo-Parthian rule.
-
B.
Kashirin
Kashirin is a Russian masculine surname commonly used in Slavic-speaking countries.
-
C.
Saratak
Saratak is a rural village located in Armenia's Shirak Province.
-
D.
Rashua
Rashua is a small volcanic island in Russia’s Kuril Islands chain in the northwest Pacific Ocean.
-
E.
Sa’och
Sa’och is an indigenous Pearic language (and its associated ethnic group) of mainland Southeast Asia, traditionally spoken by a small community in Cambodia and nearby regions.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fba7c10819095b1299b7b4f0310 |
completed | April 14, 2026, 3:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0b108908190b4b408f21ecb877a |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:22 p.m.