Triple
T34806033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paramananddas |
E1003356
|
entity |
| Predicate | praisedFormOfKrishna |
P181500
|
FINISHED |
| Object | child Krishna |
—
|
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: child Krishna | Statement: [Paramananddas, praisedFormOfKrishna, child Krishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: praisedFormOfKrishna Context triple: [Paramananddas, praisedFormOfKrishna, child Krishna]
-
A.
praisedDeity
Indicates that one entity expressed praise, admiration, or reverence toward a deity.
-
B.
depictsKrishnaAs
Indicates that one entity visually represents or portrays another entity specifically in the form or role of Krishna.
-
C.
associatedFormOfVishnu
Indicates a relationship where something is linked or connected as a particular form or manifestation of Vishnu.
-
D.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
E.
roleInGaudiyaVaishnavism
Indicates the specific function, position, or significance an entity holds within the theological, devotional, or institutional framework of Gaudiya Vaishnavism.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab085088190ace5734dcc9f1167 |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77a39135081908ae22d2a23b44e74 |
completed | May 3, 2026, 4:39 p.m. |
Created at: May 3, 2026, 3:59 p.m.