Triple
T35697681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunkeshwar Beach |
E1031487
|
entity |
| Predicate | templeProximity |
P29505
|
FINISHED |
| Object | adjacent to Kunkeshwar Temple complex |
—
|
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: adjacent to Kunkeshwar Temple complex | Statement: [Kunkeshwar Beach, templeProximity, adjacent to Kunkeshwar Temple complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeProximity Context triple: [Kunkeshwar Beach, templeProximity, adjacent to Kunkeshwar Temple complex]
-
A.
nearReligiousSite
chosen
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
B.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
C.
templeAccess
Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
-
D.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
E.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.