Triple
T17745862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulch |
E442987
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Ulch language |
—
|
NE NERFINISHED |
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: Ulch language | Statement: [Ulch, language, Ulch language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulch language Context triple: [Ulch, language, Ulch language]
-
A.
Ulch language
chosen
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.
-
B.
Udege language
The Udege language is a critically endangered Tungusic language spoken by the Udege people of the Russian Far East.
-
C.
Chulym language
The Chulym language is a critically endangered Turkic language spoken by a small indigenous community in Siberia, Russia.
-
D.
Selkup language
The Selkup language is a critically endangered Uralic (Samoyedic) language spoken by the indigenous Selkup people of western Siberia in Russia.
-
E.
Tsakhur language
The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ad26940819090696c2cb86fd606 |
completed | April 19, 2026, 6:48 a.m. |
Created at: April 10, 2026, 10:09 a.m.