Triple
T26440629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapt Kund |
E665075
|
entity |
| Predicate | pilgrimsCustomarily |
P140605
|
FINISHED |
| Object | bathe before offering prayers |
—
|
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: bathe before offering prayers | Statement: [Tapt Kund, pilgrimsCustomarily, bathe before offering prayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimsCustomarily Context triple: [Tapt Kund, pilgrimsCustomarily, bathe before offering prayers]
-
A.
pilgrimsFrom
Indicates that one or more pilgrims originate from, or are associated with coming from, a particular place.
-
B.
hasPilgrims
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
-
C.
pilgrimsPerform
chosen
Indicates that pilgrims carry out or engage in a particular religious act, ritual, or practice.
-
D.
pilgrimsObtain
Indicates that pilgrims acquire, receive, or come into possession of something.
-
E.
primaryPilgrims
Indicates that the referenced entities are the main or principal participants undertaking a pilgrimage in relation to something or someone.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6121ae1a0819083492db2e6863175 |
completed | May 2, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:58 p.m.