Triple
T38467311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Улица Старокачаловская |
E912606
|
entity |
| Predicate | официальныйЯзыкТопонима |
P189481
|
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.
hasOfficialLanguageOfToponym
chosen
Indicates that a toponym is associated with an official language in which that place name is formally recognized or used.
-
B.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
C.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
-
D.
formerOfficialNameLanguage
Indicates the language in which an entity’s former official name was expressed.
-
E.
hasWritingSystemOfToponym
Indicates that a toponym is written or represented using a particular writing system.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.