Triple

T6705832
Position Surface form Disambiguated ID Type / Status
Subject Irkutsk E153001 entity
Predicate hasSisterCity P919 FINISHED
Object Ulaanbaatar E24958 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: Ulaanbaatar | Statement: [Irkutsk, hasSisterCity, Ulaanbaatar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulaanbaatar
Context triple: [Irkutsk, hasSisterCity, Ulaanbaatar]
  • A. Ulaanbaatar chosen
    Ulaanbaatar is the capital and largest city of Mongolia, serving as its political, economic, and cultural center.
  • B. Ulanqab
    Ulanqab is a prefecture-level city in central Inner Mongolia, China, known for its grassland landscapes, agriculture, and strategic position as a transportation hub.
  • C. Hohhot
    Hohhot is the capital and largest city of Inner Mongolia in northern China, known as a regional center of politics, culture, and industry.
  • D. Öndörkhaan, Mongolia
    Öndörkhaan is a town in eastern Mongolia known historically as the site where Chinese marshal Lin Biao died in a 1971 plane crash.
  • E. Bayannur
    Bayannur is a prefecture-level city in western Inner Mongolia, China, known for its agriculture along the Yellow River and its location on the edge of the Gobi Desert.
  • 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_69c68808d8d8819087369015270788fe completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d0ea8cfc819081affc73603c2cf3 completed March 27, 2026, 6:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69c77510f80c81908fe7784bdaa640c5 completed March 28, 2026, 6:28 a.m.
Created at: March 27, 2026, 2:06 p.m.