Triple
T11008427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan Empire |
E260180
|
entity |
| Predicate | religion |
P45
|
FINISHED |
| Object | Bon |
E373244
|
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: Bon | Statement: [Tibetan Empire, religion, Bon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bon Context triple: [Tibetan Empire, religion, 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 widely known nickname of legendary American college football coach Bo Schembechler, famed for his long tenure at the University of Michigan.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7978810208190b8e2966ae67b6314 |
completed | April 9, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e37498b9fc8190860acede4f49ea4a |
completed | April 18, 2026, 12:10 p.m. |
Created at: April 8, 2026, 9:25 p.m.