Triple
T19212782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganapati Atharvashirsha |
E480394
|
entity |
| Predicate | invokedBefore |
P135003
|
FINISHED |
| Object | commencement of rituals |
—
|
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: commencement of rituals | Statement: [Ganapati Atharvashirsha, invokedBefore, commencement of rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokedBefore Context triple: [Ganapati Atharvashirsha, invokedBefore, commencement of rituals]
-
A.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than another.
-
B.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
C.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
D.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
E.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
- F. None of above. chosen
Provenance (4 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa37fc7881908c53e332625dcdb4 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:21 p.m.