Triple
T25693268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vadakalai |
E644252
|
entity |
| Predicate | honorsAcharya |
P2354
|
FINISHED |
| Object | Vedanta Desika |
—
|
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: Vedanta Desika | Statement: [Vadakalai, honorsAcharya, Vedanta Desika]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsAcharya Context triple: [Vadakalai, honorsAcharya, Vedanta Desika]
-
A.
associatedWithAcharya
Indicates a relationship in which an entity is connected, linked, or related in some relevant way to an acharya (a spiritual or scholarly teacher).
-
B.
honors
chosen
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
C.
honoursAchievement
Indicates that one entity formally recognizes and celebrates the notable accomplishment or success of another entity.
-
D.
honorsAspectOf
Indicates that one entity shows respect, recognition, or reverence specifically toward a particular aspect, quality, or facet of another entity.
-
E.
honorsNimbarkaAs
Indicates that someone regards Nimbarka with a particular status, role, or title, such as a teacher, authority, or incarnation.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 8:31 p.m.