Triple
T25678687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodhisattva |
E643876
|
entity |
| Predicate | stageSystem |
P160270
|
FINISHED |
| Object | ten bhūmis |
—
|
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: ten bhūmis | Statement: [Bodhisattva, stageSystem, ten bhūmis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageSystem Context triple: [Bodhisattva, stageSystem, ten bhūmis]
-
A.
stageTechnology
Indicates that a particular technology is used, implemented, or deployed at a specific stage or phase within a process, workflow, or lifecycle.
-
B.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
C.
stageEnvironment
Indicates that an entity is placed into or operates within a non-production (staging) environment used for testing or pre-deployment.
-
D.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
E.
stageContext
Indicates the situational or environmental setting in which an event, action, or interaction takes place.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f601f106a08190ad7b4537223dbd8c |
completed | May 2, 2026, 1:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 21, 2026, 7:43 p.m.