Triple
T176384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian language |
E3584
|
entity |
| Predicate | standardFormBasedOn |
P7430
|
FINISHED |
| Object | Moscow dialect |
—
|
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: Moscow dialect | Statement: [Russian language, standardFormBasedOn, Moscow dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardFormBasedOn Context triple: [Russian language, standardFormBasedOn, Moscow dialect]
-
A.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
B.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
C.
establishedInCurrentForm
Indicates the point in time when something took on its present structure, organization, or configuration, distinct from any earlier versions or forms.
-
D.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
E.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
- F. None of above. chosen
Provenance (4 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e497788190aeb61d981efb4d1d |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25669d99481908c5e82ba8641205a |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a258b30f6c8190be2181f30c40e04d |
completed | Feb. 28, 2026, 2:53 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.