Triple
T9630024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zavrazhye |
E232775
|
entity |
| Predicate | isInhabitedLocalityCategory |
P87153
|
FINISHED |
| Object | rural locality |
—
|
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: rural locality | Statement: [Zavrazhye, isInhabitedLocalityCategory, rural locality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInhabitedLocalityCategory Context triple: [Zavrazhye, isInhabitedLocalityCategory, rural locality]
-
A.
isInhabitedLocalityType
chosen
Indicates that an entity is classified as a specific type of inhabited locality (such as a city, town, or village).
-
B.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
C.
isInhabitedRegion
Indicates that a region has living beings (such as humans or animals) residing within its boundaries.
-
D.
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.
-
E.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b01863c8190a9ec4684804f96bc |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.