Triple
T4314371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozhaysk Reservoir |
E94151
|
entity |
| Predicate | languageOfSurroundingRegion |
P10892
|
FINISHED |
| Object | Russian |
—
|
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: Russian | Statement: [Mozhaysk Reservoir, languageOfSurroundingRegion, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfSurroundingRegion Context triple: [Mozhaysk Reservoir, languageOfSurroundingRegion, Russian]
-
A.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
C.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
-
D.
majorityLanguageOf
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
E.
regionOfMajorLanguage
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350f4448481908be2c7df9cc71bb9 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.