Triple
T5126403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaudiya Vaishnavism |
E115594
|
entity |
| Predicate | regardsChaitanyaAs |
P54588
|
FINISHED |
| Object | combined form of Radha and Krishna |
—
|
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: combined form of Radha and Krishna | Statement: [Gaudiya Vaishnavism, regardsChaitanyaAs, combined form of Radha and Krishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardsChaitanyaAs Context triple: [Gaudiya Vaishnavism, regardsChaitanyaAs, combined form of Radha and Krishna]
-
A.
regards
chosen
Indicates that one entity considers, views, or treats another entity in a particular way or with a certain attitude.
-
B.
respectedAs
Indicates that one entity regards another with esteem or honor, recognizing their value, status, or authority.
-
C.
givenAs
Indicates that something is provided, presented, or assigned to a recipient in a specified role, form, or capacity.
-
D.
regardsSufferingAs
Indicates how an entity perceives, evaluates, or emotionally responds to the suffering of another entity.
-
E.
paysHomageTo
Indicates that one entity formally shows respect, reverence, or honor toward another, often acknowledging its superiority, influence, or authority.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:42 p.m.