Triple
T31706897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanwariya |
E809204
|
entity |
| Predicate | typicalPilgrimageRouteIncludes |
P38487
|
FINISHED |
| Object | Ganges river |
E4044
|
NE 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: Ganges river | Statement: [Kanwariya, typicalPilgrimageRouteIncludes, Ganges river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPilgrimageRouteIncludes Context triple: [Kanwariya, typicalPilgrimageRouteIncludes, Ganges river]
-
A.
containsPilgrimageCircuit
Indicates that a location or area includes within it a defined route or set of sites followed as part of a pilgrimage.
-
B.
pilgrimageRouteTo
chosen
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
C.
pilgrimageStartingPoint
Indicates the location from which a pilgrimage journey is initiated or begins.
-
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.
hasPilgrimageRouteType
Indicates that a pilgrimage route is associated with a specific type or category of pilgrimage path.
- F. None of above.
Provenance (4 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f3b647ec4819091dc76f2a6ae6216 |
completed | June 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:14 p.m.