Triple
T31207246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamwe Township |
E795634
|
entity |
| Predicate | isUrbanTownshipOf |
P130506
|
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: [Tamwe Township, isUrbanTownshipOf, Yangon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanTownshipOf Context triple: [Tamwe Township, isUrbanTownshipOf, Yangon]
-
A.
isUrbanLocality
Indicates that a place is classified as an urban settlement or locality, as opposed to a rural area.
-
B.
isUrbanSettlementIn
chosen
Indicates that an urban settlement (such as a city or town) is located within a specified larger geographic or administrative area.
-
C.
isUrbanLocalGovernmentUnitOf
Indicates that one entity functions as the urban local government authority responsible for administering the other entity.
-
D.
isUrbanizedAround
Indicates that an area or region has developed urban characteristics or infrastructure surrounding a particular location or feature.
-
E.
isUrbanAreaOfType
Indicates that a given area is classified as belonging to a specific type or category of urban area (e.g., city, town, suburb).
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c2413f48190aca2109cbe0bd571 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.