Triple
T16126560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | сомони |
E391286
|
entity |
| Predicate | официальноеНазваниеНаРусском |
P20560
|
FINISHED |
| Object | сомони |
—
|
LITERAL 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: сомони | Statement: [сомони, официальноеНазваниеНаРусском, сомони]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: официальноеНазваниеНаРусском Context triple: [сомони, официальноеНазваниеНаРусском, сомони]
-
A.
nameInRussian
chosen
Indicates that an entity is known or referred to by a specific name when expressed in the Russian language.
-
B.
hasOfficialNameInJapanese
Indicates that an entity has an official, formally recognized name expressed in the Japanese language.
-
C.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
D.
hasOfficialNameInChuvash
Indicates that an entity has an official or formally recognized name expressed in the Chuvash language.
-
E.
translationOfOfficialName
Indicates that one name is an official translation of another name in a different language.
- F. None of above.
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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20204fb408190b58d49d0d64bb740 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.