Triple
T11539836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khimki Urban Okrug |
E273643
|
entity |
| Predicate | hasTypeOfDivision |
P15261
|
FINISHED |
| Object | municipal division |
—
|
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: municipal division | Statement: [Khimki Urban Okrug, hasTypeOfDivision, municipal division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDivision Context triple: [Khimki Urban Okrug, hasTypeOfDivision, municipal division]
-
A.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
B.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
C.
hasDivisionCode
Indicates that an entity is associated with a specific division identifier or code within an organizational or classification structure.
-
D.
typeOfDivision
chosen
Indicates the specific category or kind of division that characterizes how something is separated, organized, or partitioned.
-
E.
isPartOfDivision
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886deed5c81908e5c38156064f882 |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.