Triple

T18886512
Position Surface form Disambiguated ID Type / Status
Subject Kangrinboqê Peak E461970 entity
Predicate religiousSignificanceIn P6906 FINISHED
Object Bon NE NERFINISHED

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: Bon | Statement: [Kangrinboqê Peak, religiousSignificanceIn, Bon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bon
Context triple: [Kangrinboqê Peak, religiousSignificanceIn, Bon]
  • A. Bon chosen
    Bon is an ancient Tibetan spiritual tradition and religion, distinct from but historically intertwined with Buddhism, that encompasses rituals, cosmology, and practices rooted in the pre-Buddhist culture of Tibet.
  • B. Bo
    Bo was an extinct indigenous language of the Great Andamanese people, once spoken in the Andaman Islands of India.
  • C. Bo
    Bo is a masculine given name commonly used in Scandinavian countries and parts of Europe.
  • D. Bo
    Bo was the early capital city of the Shang dynasty in ancient China, serving as a major political and cultural center.
  • E. Bo
    Bo is the second-largest city in Sierra Leone and a major economic and educational center in the country's Southern Province.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c4760d808190b502c4ed1f24424c completed April 20, 2026, 6:15 a.m.
Created at: April 10, 2026, 11:58 a.m.