Triple
T2303265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shravakas |
E51778
|
entity |
| Predicate | perform |
P2297
|
FINISHED |
| Object | daily worship (puja) |
—
|
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: daily worship (puja) | Statement: [Shravakas, perform, daily worship (puja)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perform Context triple: [Shravakas, perform, daily worship (puja)]
-
A.
performed
chosen
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
B.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
C.
performance
Indicates that one entity’s effectiveness, quality, or success in carrying out a task, function, or role is being evaluated or characterized in relation to some standard or expectation.
-
D.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
E.
originalPerformanceFor
Indicates that one entity is the original performance or execution from which another related version, recording, or representation is derived.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.