Triple
T38079089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rgyal chen bzhi |
E950801
|
entity |
| Predicate | directionGuardedBy |
P197283
|
FINISHED |
| Object | Vaiśravaṇa guards the north |
—
|
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: Vaiśravaṇa guards the north | Statement: [rgyal chen bzhi, directionGuardedBy, Vaiśravaṇa guards the north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionGuardedBy Context triple: [rgyal chen bzhi, directionGuardedBy, Vaiśravaṇa guards the north]
-
A.
directionGuarded
Indicates that one entity protects, blocks, or oversees another entity specifically from a given direction or along a particular directional axis.
-
B.
laterGuardedBy
Indicates that an entity is protected or guarded by another entity at a later time or in a subsequent state or phase.
-
C.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
gatedBy
Indicates that one entity’s access, availability, or progression is controlled or restricted by another entity acting as a gate or prerequisite.
- F. None of above. chosen
Provenance (4 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
| PDg | Predicate description generation | batch_69fe831ba4708190a5564afd7d5a4319 |
completed | May 9, 2026, 12:43 a.m. |
Created at: May 3, 2026, 4:21 p.m.