Triple
T17750814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reasi district |
E443105
|
entity |
| Predicate | religiousTourismHubFor |
P57618
|
FINISHED |
| Object | Hindu pilgrims |
—
|
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: Hindu pilgrims | Statement: [Reasi district, religiousTourismHubFor, Hindu pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousTourismHubFor Context triple: [Reasi district, religiousTourismHubFor, Hindu pilgrims]
-
A.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
B.
isPlaceOfPilgrimageFor
chosen
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
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.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841a401c8190ae1dc0ed7ae4cc26 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.