Triple
T13155533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duleevka |
E312576
|
entity |
| Predicate | inhabitedPlaceStatus |
P45139
|
FINISHED |
| Object | small settlement |
—
|
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: small settlement | Statement: [Duleevka, inhabitedPlaceStatus, small settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedPlaceStatus Context triple: [Duleevka, inhabitedPlaceStatus, small settlement]
-
A.
stateInhabited
Indicates that a particular state is (or was) lived in or occupied by a specified entity.
-
B.
humanSettlementStatus
chosen
Indicates the classification of a place in terms of its status as a human settlement (e.g., whether and how it is recognized or designated as a populated place).
-
C.
isInhabitedRegion
Indicates that a region has living beings (such as humans or animals) residing within its boundaries.
-
D.
habitationStatusOfIsland
Indicates whether an island is inhabited, uninhabited, or otherwise characterized by a particular habitation status.
-
E.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.