Triple
T35531066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanda Devi |
E1026799
|
entity |
| Predicate | pilgrimageRouteIncludes |
P127879
|
FINISHED |
| Object | Nauti village |
—
|
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: Nauti village | Statement: [Nanda Devi, pilgrimageRouteIncludes, Nauti village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimageRouteIncludes Context triple: [Nanda Devi, pilgrimageRouteIncludes, Nauti village]
-
A.
containsPilgrimageCircuit
chosen
Indicates that a location or area includes within it a defined route or set of sites followed as part of a pilgrimage.
-
B.
pilgrimageRouteTo
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
C.
hasPilgrimageRouteType
Indicates that a pilgrimage route is associated with a specific type or category of pilgrimage path.
-
D.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
E.
pilgrimageObject
Indicates that something serves as the destination, focus, or goal of a religious pilgrimage.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.