Triple
T20567584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senayan, Jakarta |
E505003
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban administrative village |
C41485
|
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: urban administrative village Context triple: [Senayan, Jakarta, instanceOf, urban administrative village]
-
A.
urban administrative area
An urban administrative area is a geographically defined part of a city or town governed by specific local authorities responsible for public services, regulation, and planning within its boundaries.
-
B.
urban-type settlement
An urban-type settlement is a semi-urban locality that exhibits some characteristics of a town or small city—such as concentrated housing, infrastructure, and non-agricultural employment—without meeting all the criteria for full city status.
-
C.
urban district portion
chosen
An urban district portion is a defined sub-area within a larger urban district, characterized by specific land uses, physical features, or administrative functions that distinguish it from other parts of the district.
-
D.
urban island community
An urban island community is a densely populated, self-contained neighborhood or district surrounded by water within or adjacent to a city, blending metropolitan infrastructure with the social and environmental characteristics of island living.
-
E.
urban-rural gmina
An urban-rural gmina is a Polish administrative district that includes both a town (urban area) and its surrounding villages and countryside (rural areas) under a single local government.
- F. None of above.
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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:39 a.m.