Triple
T25811746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonogiri |
E650130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regency-level town |
C51020
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regency-level town Context triple: [Wonogiri, instanceOf, regency-level town]
-
A.
Renaissance town
A Renaissance town is an urban settlement characterized by humanist-inspired planning, harmonious proportions, and architecture that blends classical forms with emerging civic, commercial, and cultural functions of the 14th–17th centuries.
-
B.
modern town
A modern town is a moderately sized, planned settlement featuring contemporary infrastructure, diverse housing, commercial centers, public services, and digital connectivity that support the daily lives of its residents.
-
C.
rural town
A rural town is a small, sparsely populated community situated in the countryside, typically characterized by close-knit social ties, limited infrastructure, and an economy often based on agriculture or local resource industries.
-
D.
17th-century town
A 17th-century town is a small, historically situated settlement characterized by pre-industrial architecture, localized trade and governance, and social life organized around markets, churches, and craft guilds.
-
E.
royal town
A royal town is a settlement granted special status, privileges, or historical significance due to its close association with a monarchy, such as hosting royal residences, ceremonies, or administrative functions.
- F. None of above. chosen
Provenance (1 batch)
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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:10 a.m.