Triple
T23765078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ānandavallī |
E587355
|
entity |
| Predicate | hasScriptureTradition |
P16943
|
FINISHED |
| Object | Vedic |
—
|
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: Vedic | Statement: [Ānandavallī, hasScriptureTradition, Vedic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptureTradition Context triple: [Ānandavallī, hasScriptureTradition, Vedic]
-
A.
languageOfScripturalTradition
Indicates the language in which a given scriptural or religious textual tradition is expressed or transmitted.
-
B.
sharesScripturalTraditionWith
chosen
Indicates that two entities are connected by drawing on, recognizing, or being grounded in the same or closely related body of scriptural texts or religious canon.
-
C.
theologicalTradition
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
D.
hasScriptTradition
Indicates that one entity follows, preserves, or is associated with a particular script or writing tradition used for representation or transmission.
-
E.
hasRiteOrTradition
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb4e9248190b64b063637b66702 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.