Triple
T30136664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Гагаринский район |
E766012
|
entity |
| Predicate | hasTypeOfLocalSelfGovernment |
P73614
|
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: [Гагаринский район, hasTypeOfLocalSelfGovernment, муниципальный район]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfLocalSelfGovernment Context triple: [Гагаринский район, hasTypeOfLocalSelfGovernment, муниципальный район]
-
A.
hasLocalSelfGovernment
Indicates that an entity possesses its own local governing authority with decision-making powers over local affairs.
-
B.
hasLocalGovernmentBody
Indicates that an entity is administered or overseen by a specific local government authority or governing body.
-
C.
hasCityGovernmentType
chosen
Indicates the specific form or structure of municipal governance that administers a city.
-
D.
hasLocalGovernmentSystem
Indicates that an entity possesses or operates under a particular system or structure of local government.
-
E.
isLocalGovernment
Indicates that an entity functions as a governing body with authority over a specific local or regional area within a larger political 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 29, 2026, 7:16 p.m.