Triple

T14883078
Position Surface form Disambiguated ID Type / Status
Subject Maha Bandula E350048 entity
Predicate placeOfDeath P21 FINISHED
Object Danubyu E1091383 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: Danubyu | Statement: [Maha Bandula, placeOfDeath, Danubyu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Danubyu
Context triple: [Maha Bandula, placeOfDeath, Danubyu]
  • A. Danubyu chosen
    Danubyu is a town in Myanmar’s Ayeyarwady Region, historically notable as the site of a major engagement during the First Anglo-Burmese War.
  • B. Didube
    Didube is a metro station in Tbilisi, Georgia, serving as a key transit hub that connects the city’s metro system with major bus and marshrutka routes to other regions.
  • C. Yambu
    Yambu is a coastal city in western Saudi Arabia on the Red Sea, known as an important port and industrial center.
  • D. Bayabas
    Bayabas is a coastal municipality in the Philippine province of Surigao del Sur known for its fishing communities and rural seaside landscapes.
  • E. Dule
    Dule are the Indigenous Guna people’s self-designation, referring to themselves as a distinct Native group of Panama and Colombia.
  • 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.