Triple
T19950020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nageshwar Jyotirlinga Temple |
E479528
|
entity |
| Predicate | hasPrasadDistribution |
P133355
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nageshwar Jyotirlinga Temple, hasPrasadDistribution, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrasadDistribution Context triple: [Nageshwar Jyotirlinga Temple, hasPrasadDistribution, yes]
-
A.
hasMainPrasad
Indicates that an entity is associated with or provides the primary sacred offering (main prasad) in a religious or ceremonial context.
-
B.
offersPrasadam
chosen
Indicates that one entity provides or distributes consecrated food (prasadam) to another entity.
-
C.
hasDistributions
Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
-
D.
hasChhatri
Indicates that one entity possesses or features a chhatri (a dome-shaped pavilion or canopy structure) in relation to another entity or location.
-
E.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6a93548190875af2176e6901a7 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.