Triple
T8848173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клушино |
E210561
|
entity |
| Predicate | языкМестногоНаселения |
P77346
|
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.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
B.
majorityLanguageOf
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
C.
languageOfLocalOrganization
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
D.
demographicsSignificantLanguage
Indicates that a particular language is significantly represented or prevalent within the demographic profile of a population or group.
-
E.
hasLanguageInhabitants
chosen
Indicates that a particular language is spoken or used by the inhabitants of a specified place or region.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60aa6db0819097c3257499200afc |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.