Triple
T20747302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samantabhadra |
E510618
|
entity |
| Predicate | positionInTrikayaContext |
P141345
|
FINISHED |
| Object | associated with Dharmakaya |
—
|
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: associated with Dharmakaya | Statement: [Samantabhadra, positionInTrikayaContext, associated with Dharmakaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTrikayaContext Context triple: [Samantabhadra, positionInTrikayaContext, associated with Dharmakaya]
-
A.
positionOnTrident
Indicates that one entity occupies a specific location or slot on a trident-like structure or configuration.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
positionInSriYantra
Indicates the specific spatial location or role that an element occupies within the geometric structure of the Sri Yantra.
-
E.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c226fbf881909794eff3ee9e206b |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:33 p.m.