Triple
T902962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adi Shankaracharya |
E19484
|
entity |
| Predicate | roleInHinduism |
P2319
|
FINISHED |
| Object | revival of Vedic traditions |
—
|
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: revival of Vedic traditions | Statement: [Adi Shankaracharya, roleInHinduism, revival of Vedic traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHinduism Context triple: [Adi Shankaracharya, roleInHinduism, revival of Vedic traditions]
-
A.
roleInTheology
chosen
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
B.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
E.
religiousCalendarRole
Indicates a role or function that something or someone has within a religious calendar, such as marking, organizing, or defining religious dates or observances.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad56f4c08190a7a5091ff0eb3209 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa98caec8190bbcc38320090f058 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.