Triple

T3731634
Position Surface form Disambiguated ID Type / Status
Subject Druk Gyalpo E79076 entity
Predicate residence P75 FINISHED
Object Lingkana Palace E311763 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: Lingkana Palace | Statement: [Druk Gyalpo, residence, Lingkana Palace]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lingkana Palace
Context triple: [Druk Gyalpo, residence, Lingkana Palace]
  • A. Lingkana Palace chosen
    Lingkana Palace is the royal residence in Thimphu, Bhutan, serving as the home of the reigning Dragon King and the Bhutanese royal family.
  • B. Haga Palace
    Haga Palace is a historic royal residence in Sweden, located within Haga Park just north of central Stockholm.
  • C. Huliheʻe Palace
    Huliheʻe Palace is a historic former royal residence on the Big Island of Hawaiʻi that now serves as a museum showcasing Hawaiian monarchy-era artifacts and culture.
  • D. Bonde Palace
    Bonde Palace is a historic 17th-century Baroque building in Stockholm that now serves as the seat of Sweden’s Supreme Court.
  • E. Monsoon Palace
    Monsoon Palace is a hilltop royal residence overlooking Udaipur, Rajasthan, famed for its panoramic views of the city, surrounding lakes, and Aravalli hills.
  • 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_69ad8b0e4650819090ad7cef094285e8 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcb21002c81908438170ed6f6c271 completed March 8, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4db167c5881909772cf1e78717995 completed March 14, 2026, 3:50 a.m.
Created at: March 8, 2026, 3:34 p.m.