Triple
T14968118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bon |
E373244
|
entity |
| Predicate | hasStatusInTibet |
P35203
|
FINISHED |
| Object | recognized religious tradition |
—
|
LITERAL 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: recognized religious tradition | Statement: [Bon, hasStatusInTibet, recognized religious tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInTibet Context triple: [Bon, hasStatusInTibet, recognized religious tradition]
-
A.
equivalentInTibet
Indicates that two entities are considered equivalent or correspond to each other within the context of Tibet.
-
B.
hasStatusInTradition
chosen
Indicates that an entity holds a particular recognized status or standing within a specified tradition or traditional framework.
-
C.
PotalaPalaceStatus
Indicates the current condition, preservation state, or functional status of the Potala Palace.
-
D.
legalStatusInChina
Indicates the legal status or standing that an entity holds under the laws and regulations of China.
-
E.
hasLandmarkStatusIn
Indicates that an entity holds a recognized landmark status within a specified geographic or administrative area.
- F. None of above.
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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e44cb0819096e09f8026ef8174 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:48 a.m.