Triple
T13064972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chudovo |
E329297
|
entity |
| Predicate | isInhabitedPlaceCategory |
P87153
|
FINISHED |
| Object | small town |
—
|
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 town | Statement: [Chudovo, isInhabitedPlaceCategory, small town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInhabitedPlaceCategory Context triple: [Chudovo, isInhabitedPlaceCategory, small town]
-
A.
isInhabitedLocalityType
chosen
Indicates that an entity is classified as a specific type of inhabited locality (such as a city, town, or village).
-
B.
isInhabitedPlaceServedBy
Indicates that a particular inhabited place is provided with services or coverage by a specified service entity (such as a facility, route, or organization).
-
C.
isPopulatedPlaceIn
Indicates that a populated place (such as a city, town, or village) is located within a specified larger geographic or administrative area.
-
D.
isInhabitedRegion
Indicates that a region has living beings (such as humans or animals) residing within its boundaries.
-
E.
isPopulatedPlace
Indicates that the subject is a geographic location where people live or have lived, such as a city, town, village, or settlement.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980eb81948190b27eb9ae19978079 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 8:59 p.m.