Triple
T18781858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gang Rinpoche |
E459275
|
entity |
| Predicate | inBon |
P37345
|
FINISHED |
| Object | sacred nine‑storey swastika mountain |
—
|
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: sacred nine‑storey swastika mountain | Statement: [Gang Rinpoche, inBon, sacred nine‑storey swastika mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inBon Context triple: [Gang Rinpoche, inBon, sacred nine‑storey swastika mountain]
-
A.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
B.
in
chosen
Indicates that one entity is located within the spatial, temporal, or conceptual bounds of another entity.
-
C.
bando
Indicates a relationship where an entity is placed under a ban, prohibition, or outlaw status imposed by some authority.
-
D.
bounty
Indicates that a reward or payment is offered for performing a specific action or achieving a particular outcome related to an entity.
-
E.
boonDetails
Indicates the specific terms, conditions, or characteristics associated with a granted benefit or favor within the relationship or action.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977d7c5c8190ab2aadb47283965d |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.