Triple
T26725891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhaktamara Stotra |
E673834
|
entity |
| Predicate | hasCommentariesIn |
P98053
|
FINISHED |
| Object | Sanskrit |
—
|
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: Sanskrit | Statement: [Bhaktamara Stotra, hasCommentariesIn, Sanskrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommentariesIn Context triple: [Bhaktamara Stotra, hasCommentariesIn, Sanskrit]
-
A.
hasCommentaryIn
chosen
Indicates that an entity is discussed, analyzed, or annotated within a specific commentary work or source.
-
B.
hasCommentaryOn
Indicates that one entity provides commentary, explanation, or evaluative remarks about another entity.
-
C.
hasCommentaryForm
Indicates that one entity exists in, or is associated with, a commentary version or format of another entity.
-
D.
hasManyCommentaries
Indicates that an entity is associated with multiple commentary records or annotations.
-
E.
isSubCommentaryOn
Indicates that one commentary functions as a subordinate or dependent commentary on another commentary, elaborating or commenting on it rather than standing alone.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 27, 2026, 3:42 a.m.