Triple
T4107604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judeo-Kermani |
E88491
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Kerman |
E214530
|
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: Kerman | Statement: [Judeo-Kermani, spokenIn, Kerman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kerman Context triple: [Judeo-Kermani, spokenIn, Kerman]
-
A.
Kerman
Kerman is a small city in California’s San Joaquin Valley, known for its agricultural economy and location west of Fresno.
-
B.
Kerman
chosen
Kerman is a major city in southeastern Iran known for its rich history, traditional bazaars, and proximity to desert landscapes.
-
C.
Birjand
Birjand is a city in eastern Iran that serves as the capital of South Khorasan Province and is known for its historical forts and saffron production.
-
D.
Yazd
Yazd is an ancient desert city in central Iran known for its well-preserved mud-brick architecture, Zoroastrian heritage, and historically significant Jewish community.
-
E.
Kermanshah
Kermanshah is a major city in western Iran known for its rich Kurdish culture and proximity to important historical and archaeological sites.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af019e23c481909578eba1c9270282 |
completed | March 9, 2026, 5:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b63725b9348190af56a6b7477de03f |
completed | March 15, 2026, 4:35 a.m. |
Created at: March 9, 2026, 3:40 p.m.