Triple
T5008793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lezgian |
E112561
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Rutul language |
E416663
|
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: Rutul language | Statement: [Lezgian, closelyRelatedTo, Rutul language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rutul language Context triple: [Lezgian, closelyRelatedTo, Rutul language]
-
A.
Rutul language
chosen
The Rutul language is a Northeast Caucasian language spoken primarily by the Rutul people in southern Dagestan, Russia, and parts of northern Azerbaijan.
-
B.
Tsakhur language
The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
-
C.
Dolgan language
The Dolgan language is a Turkic language spoken primarily by the Dolgan people of northern Siberia, particularly in Russia’s Taymyr Peninsula.
-
D.
Ulch language
The Ulch language is a critically endangered Tungusic language spoken by the Ulch people in the Russian Far East, primarily along the lower Amur River.
-
E.
Udege language
The Udege language is a critically endangered Tungusic language spoken by the Udege people of the Russian Far East.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd72eb05f881908d7dc3d7cd07b2ae |
completed | March 20, 2026, 4:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9269e72881908ea49a77a83b8958 |
completed | March 21, 2026, 12:43 p.m. |
Created at: March 20, 2026, 1:35 p.m.