Triple

T11803739
Position Surface form Disambiguated ID Type / Status
Subject Hanthawaddy Kingdom E280691 entity
Predicate capital P234 FINISHED
Object Bago E779655 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: Bago | Statement: [Hanthawaddy Kingdom, capital, Bago]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bago
Context triple: [Hanthawaddy Kingdom, capital, Bago]
  • A. Bago
    Bago is a component city in the province of Negros Occidental in the Philippines, known for its agricultural economy and historical significance.
  • B. Bago chosen
    Bago is a historic city in southern Myanmar known for its ancient Buddhist monuments and proximity to Yangon.
  • C. Bagà
    Bagà is a historic town in Catalonia, Spain, known for its medieval old quarter and location in the Pyrenees.
  • D. Bacuag
    Bacuag is a coastal municipality in the province of Surigao del Norte in the Philippines, known for its fishing communities and access to rich marine resources.
  • E. Bagana
    Bagana is an active stratovolcano on Bougainville Island in Papua New Guinea, known for its frequent eruptions and extensive lava flows.
  • 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_69d6ab26aae88190b2489efcb2a24234 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5a5a2048190b68027f622366079 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f166dbcb848190a5942ec00a2ca2f9 completed April 29, 2026, 2:03 a.m.
Created at: April 8, 2026, 9:42 p.m.