Triple
T16300390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazanderani |
E395767
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Amoli dialect |
E522459
|
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: Amoli dialect | Statement: [Mazanderani, hasDialect, Amoli dialect]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amoli dialect Context triple: [Mazanderani, hasDialect, Amoli dialect]
-
A.
Amoli dialect
chosen
The Amoli dialect is a regional variety of the Mazanderani language traditionally spoken in and around the city of Amol in northern Iran.
-
B.
Tyari dialect
The Tyari dialect is a regional variety of Assyrian Neo-Aramaic traditionally spoken by Assyrian communities from the Tyari region in the Hakkari mountains.
-
C.
Kauravi dialect
Kauravi dialect is a regional variety of Hindi-Urdu traditionally spoken in and around the Delhi region of northern India.
-
D.
Malwai dialect
The Malwai dialect is a regional variety of Punjabi primarily spoken in the Malwa region of the Indian state of Punjab.
-
E.
Sonepuri dialect
The Sonepuri dialect is a regional variety of the Koshali language spoken primarily around the Sonepur area in western Odisha, India.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e31c9e8819094593f3aeb44f2ca |
completed | April 17, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f9fb2908190a8521b1ccf49170a |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:06 a.m.