Triple
T27016230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indrayani River |
E680539
|
entity |
| Predicate | religiousEventOnBanks |
P75655
|
FINISHED |
| Object | Ashadhi Ekadashi pilgrimage |
—
|
NE NERFINISHED |
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: Ashadhi Ekadashi pilgrimage | Statement: [Indrayani River, religiousEventOnBanks, Ashadhi Ekadashi pilgrimage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousEventOnBanks Context triple: [Indrayani River, religiousEventOnBanks, Ashadhi Ekadashi pilgrimage]
-
A.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
B.
religiousEventRecognizedBy
Indicates that a religious event is formally acknowledged, validated, or accepted by a particular authority, group, or institution.
-
C.
associatedWithReligiousEvent
chosen
Indicates a relationship where something is connected or related to a specific religious event or ceremony.
-
D.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
E.
religiousEventYear
Indicates the calendar year in which a specified religious event took place or is scheduled to occur.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 27, 2026, 7:06 a.m.