Triple

T16653604
Position Surface form Disambiguated ID Type / Status
Subject Mount Victoria E404668 entity
Predicate alsoKnownAs P39 FINISHED
Object Nat Ma Taung E1183414 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: Nat Ma Taung | Statement: [Mount Victoria, alsoKnownAs, Nat Ma Taung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nat Ma Taung
Context triple: [Mount Victoria, alsoKnownAs, Nat Ma Taung]
  • A. Nat Ma Taung chosen
    Nat Ma Taung is a prominent peak in western Myanmar’s Chin Hills, renowned for its rich biodiversity and cultural significance to local Chin communities.
  • B. Yenangyaung
    Yenangyaung is a town in central Myanmar known historically as the site of a major World War II battle between Allied and Japanese forces.
  • C. Maung
    Maung is a Burmese surname commonly used in Myanmar and among the Burmese diaspora.
  • D. Maung
    Maung is an Aboriginal Australian language traditionally spoken by the Maung people of the Goulburn Islands in the Northern Territory.
  • E. Nyaung-U
    Nyaung-U is a historic town in central Myanmar best known as the main gateway to the ancient temple plain of Bagan.
  • 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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37bf861348190b2b0b5574d4ddb4f completed April 18, 2026, 12:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084c6bf8c81909b376875ae038e3f completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:18 a.m.