Triple
T21886816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandi Path |
E540425
|
entity |
| Predicate | traditionallyChantedBy |
P32287
|
FINISHED |
| Object | Hindu priests |
—
|
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: Hindu priests | Statement: [Chandi Path, traditionallyChantedBy, Hindu priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyChantedBy Context triple: [Chandi Path, traditionallyChantedBy, Hindu priests]
-
A.
isTraditionallySungBy
chosen
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
-
B.
traditionallySungAfter
Indicates that one song or musical piece is customarily performed immediately following another in a cultural or traditional sequence.
-
C.
chantingIs24x7
Indicates that the chanting activity occurs continuously, 24 hours a day, 7 days a week.
-
D.
chantingMedium
Indicates that the action or communication is performed through chanting as the medium or method.
-
E.
alsoChantedIn
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.