Triple

T9406464
Position Surface form Disambiguated ID Type / Status
Subject Sagaing Region E226599 entity
Predicate containsCity P294 FINISHED
Object Sagaing E276015 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: Sagaing | Statement: [Sagaing Region, containsCity, Sagaing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sagaing
Context triple: [Sagaing Region, containsCity, Sagaing]
  • A. Sagaing chosen
    Sagaing is a historic city in northern Myanmar known for its numerous Buddhist monasteries and pagodas spread across the hills along the Irrawaddy River.
  • B. Sandvollan
    Sandvollan is a village in the municipality of Inderøy in Trøndelag county, Norway.
  • C. Thamserku
    Thamserku is a prominent Himalayan peak in eastern Nepal, known for its steep, dramatic profile and popularity among experienced mountaineers.
  • D. Schaumainkai
    Schaumainkai is a prominent riverside street along the south bank of the Main River in Frankfurt, Germany, known for its concentration of major museums and cultural institutions.
  • E. Skaugum
    Skaugum is the official country residence of the Norwegian royal family, located in Asker near Oslo.
  • 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_69ca843280488190bc65600e843ef9e6 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd51c3fc988190ac34cc9e09f8ebfc completed April 1, 2026, 5:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1102414e8819097a1bb58a3ded630 completed April 4, 2026, 1:20 p.m.
Created at: March 30, 2026, 7:47 p.m.