Triple
T29942605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurunegala District |
E760537
|
entity |
| Predicate | hasKeyUrbanCenter |
P11388
|
FINISHED |
| Object | Kurunegala |
—
|
NE NERFINISHED |
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: Kurunegala | Statement: [Kurunegala District, hasKeyUrbanCenter, Kurunegala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyUrbanCenter Context triple: [Kurunegala District, hasKeyUrbanCenter, Kurunegala]
-
A.
isUrbanCenter
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a region.
-
B.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
-
C.
containsUrbanArea
chosen
Indicates that a geographic region fully or partially encompasses an urbanized area within its boundaries.
-
D.
hasUrbanFeature
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
-
E.
hasUrbanSectionsIn
Indicates that an entity includes or contains sections that are classified as urban within a specified area or region.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 6:23 p.m.