Triple
T9101309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Горки |
E218161
|
entity |
| Predicate | isInhabitedLocalityType |
P87153
|
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: [Горки, isInhabitedLocalityType, посёлок в России]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInhabitedLocalityType Context triple: [Горки, isInhabitedLocalityType, посёлок в России]
-
A.
isInhabitedRegion
Indicates that a region has living beings (such as humans or animals) residing within its boundaries.
-
B.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
C.
hasRuralLocality
Indicates that an entity possesses, includes, or is associated with a rural locality (such as a village, hamlet, or countryside settlement) within its scope or jurisdiction.
-
D.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
E.
isInlandSettlement
Indicates that a settlement is located away from the coast, without direct access to the sea or ocean.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc971435d08190b5007ed44ac0a364 |
completed | April 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:15 p.m.