Triple
T13206416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaik River |
E314376
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Yaik |
E250765
|
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: Yaik | Statement: [Yaik River, alsoKnownAs, Yaik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yaik Context triple: [Yaik River, alsoKnownAs, Yaik]
-
A.
Yaik
chosen
Yaik is the former name of the Ural River, a major waterway in Russia and Kazakhstan that flows from the Ural Mountains into the Caspian Sea.
-
B.
Yamskaya
Yamskaya is a name element associated with several historic streets and districts in Moscow, traditionally linked to coachmen’s settlements along major travel routes.
-
C.
Biysk
Biysk is a historic industrial city in southwestern Siberia, Russia, situated on the Biya River and serving as a key gateway to the Altai Mountains.
-
D.
Yenakiieve
Yenakiieve is an industrial city in eastern Ukraine, historically known for its coal mining and metallurgical industries.
-
E.
Yakut
Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9b0cf08190a1d71cc94139539d |
completed | April 10, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f60eee288190bdb3ed6110394e48 |
completed | May 3, 2026, 7:15 a.m. |
Created at: April 9, 2026, 9:17 p.m.