Triple
T1219753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayodhya |
E26191
|
entity |
| Predicate | pilgrimageType |
P20225
|
FINISHED |
| Object | Hindu pilgrimage site |
—
|
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 pilgrimage site | Statement: [Ayodhya, pilgrimageType, Hindu pilgrimage site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimageType Context triple: [Ayodhya, pilgrimageType, Hindu pilgrimage site]
-
A.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
B.
isPilgrimageDestination
chosen
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
C.
pilgrimageImportance
Indicates the degree to which something holds religious or spiritual significance as a destination or object of pilgrimage.
-
D.
pilgrimageFestivalsObserved
Indicates that certain pilgrimage-related religious festivals are practiced or observed by the subject.
-
E.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be1d55a08190a138b2411a7c4376 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.