Triple
T32315734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanayethazan Township |
E825626
|
entity |
| Predicate | locatedInUrbanCoreOf |
P12103
|
FINISHED |
| Object | Mandalay |
E57185
|
NE 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: Mandalay | Statement: [Chanayethazan Township, locatedInUrbanCoreOf, Mandalay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInUrbanCoreOf Context triple: [Chanayethazan Township, locatedInUrbanCoreOf, Mandalay]
-
A.
withinUrbanArea
chosen
Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
-
B.
urbanCoreCity
Indicates that a city functions as the primary urban core or central city within a larger metropolitan or urban area.
-
C.
isDowntownCoreOf
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
-
D.
locatedInUrbanizationType
Indicates that one entity is situated within, or belongs to, a specific type or category of urbanized area (e.g., city, suburb, metropolitan zone).
-
E.
containsUrbanArea
Indicates that a geographic region fully or partially encompasses an urbanized area within its boundaries.
- F. None of above.
Provenance (4 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0248062e608190aae1afdae38d2e5a |
completed | May 11, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3485efe1488190bd996d220e0e356b |
completed | June 18, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a02465a0d38819084c3a6813fb943fc |
completed | May 11, 2026, 9:12 p.m. |
Created at: May 1, 2026, 12:46 a.m.