Triple
T14883149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Prome |
E350050
|
entity |
| Predicate | hasLocation |
P40
|
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: [Siege of Prome, hasLocation, Pyay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyay Context triple: [Siege of Prome, hasLocation, 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.
Paya
Paya is a small settlement located within Panama’s Darién Province, known for its remote jungle environment and proximity to the Darién Gap.
-
C.
Palapye
Palapye is a rapidly growing town in central Botswana that serves as a key commercial and transport hub along the country’s main north–south corridor.
-
D.
La Paya
La Paya is an important pre-Columbian archaeological site in northwest Argentina associated with the Calchaquí culture, known for its extensive ruins and artifacts.
-
E.
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.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e7c0e48190af2d68a71130585c |
completed | April 15, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b5af8208190a35451477ea20b03 |
completed | May 8, 2026, 11:01 p.m. |
Created at: April 10, 2026, 1:56 a.m.