Triple
T5375436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ananta |
E108947
|
entity |
| Predicate | relationshipToVishnu |
P60881
|
FINISHED |
| Object | servant of Vishnu |
—
|
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: servant of Vishnu | Statement: [Ananta, relationshipToVishnu, servant of Vishnu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToVishnu Context triple: [Ananta, relationshipToVishnu, servant of Vishnu]
-
A.
relationshipToDeities
chosen
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
B.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
C.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
D.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
E.
relationshipToAtmanInVishishtadvaita
Indicates the specific theological relationship that an entity bears to the Ātman (self) as understood within the Vishishtadvaita (qualified non-dualism) philosophical framework.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.