Triple
T19599507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenki people |
E470429
|
entity |
| Predicate | exonym |
P4705
|
FINISHED |
| Object | Tungus |
—
|
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: Tungus | Statement: [Evenki people, exonym, Tungus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tungus Context triple: [Evenki people, exonym, Tungus]
-
A.
Tungus
chosen
Tungus is an older term historically used to refer to the Evenki people and their language of Siberia.
-
B.
Tunguska River
The Tunguska River is a river in the Russian Far East that flows through the sparsely populated taiga landscapes of Khabarovsk Krai before joining larger regional waterways.
-
C.
Podkamennaya Tunguska River
The Podkamennaya Tunguska River is a major Siberian river in Russia, best known for the 1908 Tunguska event that occurred near its basin.
-
D.
Yakut
Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
-
E.
Ozyornaya
Ozyornaya is a Moscow Metro station on the Kalininsko–Solntsevskaya Line serving the western part of the city.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407d46188190b9818665b2a698a5 |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.