Triple
T5846823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Iranian languages |
E129731
|
entity |
| Predicate | hasNotableLanguage |
P7390
|
FINISHED |
| Object | Ormuri |
E228139
|
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: Ormuri | Statement: [Southeastern Iranian languages, hasNotableLanguage, Ormuri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ormuri Context triple: [Southeastern Iranian languages, hasNotableLanguage, Ormuri]
-
A.
Ormur
chosen
Ormur is a lesser-known Eastern Iranian language spoken primarily by the Ormur people in parts of Afghanistan and Pakistan.
-
B.
Dromi
Dromi is a mythical chain in Norse mythology that was used in an early attempt to bind the monstrous wolf Fenrir.
-
C.
Morvi
Morvi is a town in the Morbi district of Gujarat, India, historically known as the seat of the former princely Morvi State.
-
D.
Umroi
Umroi is a town in the Indian state of Meghalaya known for serving as the location of Shillong’s main airport.
-
E.
Rigmor
Rigmor is a feminine given name of Scandinavian origin, particularly used in Norway and Denmark.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0351157508190a78d2a7141e0cee8 |
completed | March 22, 2026, 6:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a1ad4d888190b4a1e605887b2e2c |
completed | March 23, 2026, 2:13 a.m. |
Created at: March 22, 2026, 3:55 p.m.