Triple

T26525941
Position Surface form Disambiguated ID Type / Status
Subject Hlegu Township E670687 entity
Predicate isPeriUrbanHinterlandOf P110494 FINISHED
Object Yangon 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: Yangon | Statement: [Hlegu Township, isPeriUrbanHinterlandOf, Yangon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPeriUrbanHinterlandOf
Context triple: [Hlegu Township, isPeriUrbanHinterlandOf, Yangon]
  • A. hasRuralHinterland
    Indicates that a place or urban area is associated with and served by a surrounding rural region that supports it economically, socially, or functionally.
  • B. isSuburbanRuralFringeOf chosen
    Indicates that one area lies on the outer edge or transition zone between a suburban region and the surrounding rural countryside of another area.
  • C. isUrbanizedAround
    Indicates that an area or region has developed urban characteristics or infrastructure surrounding a particular location or feature.
  • D. isUrbanLocality
    Indicates that a place is classified as an urban settlement or locality, as opposed to a rural area.
  • E. hasPeriUrbanPopulation
    Indicates that an entity has a population living in peri-urban areas, i.e., zones at the transition between urban and rural regions.
  • 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_69eeb31ea1e08190b9ff43cf9bc25bf8 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f613c628008190b4676558dcf17d65 completed May 2, 2026, 3:09 p.m.
PD Predicate disambiguation batch_69f602d7b1b0819095ddd3b5169f8ce2 completed May 2, 2026, 1:57 p.m.
Created at: April 27, 2026, 1:31 a.m.