Triple
T9125642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yangon Central Railway Station |
E218960
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Pyay |
E239253
|
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: Pyay | Statement: [Yangon Central Railway Station, connectsTo, Pyay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyay Context triple: [Yangon Central Railway Station, connectsTo, Pyay]
-
A.
Pyay
chosen
Pyay is a historic town in central Myanmar known as a regional trading center and gateway to the ancient Pyu archaeological sites of Sri Ksetra.
-
B.
Yandabo
Yandabo is a village in central Myanmar historically notable as the site where the Treaty of Yandabo ended the First Anglo-Burmese War in 1826.
-
C.
Ko Payan
Ko Payan is one of the smaller islands within Thailand’s Similan Islands archipelago, known for its clear waters, coral reefs, and rich marine life.
-
D.
Nayapala
Nayapala was a ruler of the Pala dynasty in eastern India, known for consolidating Pala power in Bengal and Bihar during the 11th century.
-
E.
Poh Pitu
Poh Pitu was an early capital city of the Medang Kingdom, an ancient Javanese Hindu-Buddhist polity in what is now Indonesia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b8970881909c3b2c67fc131627 |
completed | April 1, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d030a1042c8190a31c76638a95a2cf |
completed | April 3, 2026, 9:26 p.m. |
Created at: March 30, 2026, 7:17 p.m.