Triple
T10127402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Turkic branch |
E226248
|
entity |
| Predicate | includesLanguage |
P2177
|
FINISHED |
| Object | Dolgan |
E233989
|
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: Dolgan | Statement: [Common Turkic branch, includesLanguage, Dolgan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dolgan Context triple: [Common Turkic branch, includesLanguage, Dolgan]
-
A.
Dolgan
chosen
Dolgan is a Turkic language spoken primarily by the Dolgan people in northern Siberia, especially in Russia’s Taymyr Peninsula.
-
B.
Dolgoch
Dolgoch is a historic narrow-gauge steam locomotive on Wales’s Talyllyn Railway, renowned for its preservation-era significance and distinctive Victorian design.
-
C.
Dzherman
Dzherman is a river in southwestern Bulgaria that serves as a significant tributary of the Struma River.
-
D.
Oreshek
Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
-
E.
Golymin
Golymin is a village in east-central Poland best known as the site of a significant engagement during the Napoleonic Wars.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2eef7388190b95ffd02814f2d1f |
completed | April 2, 2026, 2:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e5c29f6c8190b347a6963ca46dac |
completed | April 5, 2026, 10:44 p.m. |
Created at: March 30, 2026, 9:05 p.m.