Triple
T17937867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudarshana Homa |
E448514
|
entity |
| Predicate | consideredAspectOf |
P128794
|
FINISHED |
| Object | Vedic yajna tradition |
—
|
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 yajna tradition | Statement: [Sudarshana Homa, consideredAspectOf, Vedic yajna tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredAspectOf Context triple: [Sudarshana Homa, consideredAspectOf, Vedic yajna tradition]
-
A.
governsAspectOf
Indicates that one entity exercises control, regulation, or determining influence over a particular aspect or component of another entity.
-
B.
consideredPartOf
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
C.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
-
D.
conceptualAspect
chosen
Indicates that one entity represents an abstract, conceptual, or non-physical aspect, feature, or dimension of another entity.
-
E.
coversAspect
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad937f0881909d22ac8c2be9e35e |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.