Triple
T25445877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadhak Bamakhepa |
E637635
|
entity |
| Predicate | spiritualReputation |
P79418
|
FINISHED |
| Object | revered as a siddha |
—
|
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: revered as a siddha | Statement: [Sadhak Bamakhepa, spiritualReputation, revered as a siddha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualReputation Context triple: [Sadhak Bamakhepa, spiritualReputation, revered as a siddha]
-
A.
pietyReputation
chosen
Indicates the degree to which an entity is regarded as devout, virtuous, or religiously upright based on its perceived behavior or character.
-
B.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
C.
spiritualPatron
Indicates that one entity serves as a guiding or protective spiritual figure or patron for another entity.
-
D.
spiritualityCharacteristic
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
-
E.
placeInReputation
Indicates that an entity holds a particular standing, status, or level within a reputation or ranking system.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f70346cc8190b7ed6b5a86a508cd |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:01 p.m.