Triple
T21726756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tskhumi |
E536293
|
entity |
| Predicate | usedInLanguage |
P907
|
FINISHED |
| Object | Laz 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: Laz language | Statement: [Tskhumi, usedInLanguage, Laz language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laz language Context triple: [Tskhumi, usedInLanguage, Laz language]
-
A.
Laz language
chosen
The Laz language is a South Caucasian (Kartvelian) minority language spoken mainly along the Black Sea coast of Turkey and Georgia.
-
B.
Larat language
The Larat language is an Austronesian language spoken on Larat Island in Indonesia’s Tanimbar archipelago.
-
C.
Lasalimu language
The Lasalimu language is an Austronesian language spoken by a small community on Buton Island in Southeast Sulawesi, Indonesia.
-
D.
Lashi language
Lashi language is a Tibeto-Burman language spoken by the Lashi people, primarily in parts of Myanmar and China, and is closely related to Jingpho and other languages of the Bodo–Konyak–Jingpho branch.
-
E.
Zay language
Zay language is a South Ethiopic Semitic language spoken by the Zay people on islands and shores of Lake Zway in Ethiopia.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd973ac648190bb09e20ac1be2d9b |
completed | April 27, 2026, 9:47 p.m. |
Created at: April 16, 2026, 6:48 p.m.