Triple
T24272876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navadvip Mandala Parikrama |
E605327
|
entity |
| Predicate | religiousActivityType |
P21643
|
FINISHED |
| Object | yatra |
—
|
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: yatra | Statement: [Navadvip Mandala Parikrama, religiousActivityType, yatra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousActivityType Context triple: [Navadvip Mandala Parikrama, religiousActivityType, yatra]
-
A.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
B.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
C.
religiousSupportType
Indicates the type or form of support provided or received in a religious or faith-based context.
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
religiousOrRitualAssociation
Indicates a connection between entities based on shared religious, spiritual, or ritual practices, roles, or significance.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5c8f588190866d5b5cb3f290fe |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.