Triple
T19594269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vajapeya |
E470310
|
entity |
| Predicate | performedForDeity |
P16947
|
FINISHED |
| Object | multiple Vedic deities |
—
|
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: multiple Vedic deities | Statement: [Vajapeya, performedForDeity, multiple Vedic deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedForDeity Context triple: [Vajapeya, performedForDeity, multiple Vedic deities]
-
A.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
B.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
-
C.
involvesDeity
chosen
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the relationship.
-
D.
portraysDeity
Indicates that one entity represents, depicts, or characterizes another entity as a deity or divine being.
-
E.
pursuesDeity
Indicates that one entity actively seeks, follows, or strives to attain or engage with a deity.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640793cd88190b9b84491bfb2493f |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.