Triple
T32911275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jogulamba Temple |
E841882
|
entity |
| Predicate | nearbyTempleGroup |
P29505
|
FINISHED |
| Object | Navabrahma temples of Alampur |
—
|
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: Navabrahma temples of Alampur | Statement: [Jogulamba Temple, nearbyTempleGroup, Navabrahma temples of Alampur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyTempleGroup Context triple: [Jogulamba Temple, nearbyTempleGroup, Navabrahma temples of Alampur]
-
A.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
B.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
C.
nearReligiousSite
chosen
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
D.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
E.
nearbyGhats
Indicates that one location is situated close to or in the immediate vicinity of a ghat (such as a riverfront or stepped embankment).
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 1:19 a.m.