Triple
T32889031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navabrahma temples |
E841280
|
entity |
| Predicate | nearbyDeityTemple |
P149744
|
FINISHED |
| Object | Jogulamba Temple |
—
|
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: Jogulamba Temple | Statement: [Navabrahma temples, nearbyDeityTemple, Jogulamba Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyDeityTemple Context triple: [Navabrahma temples, nearbyDeityTemple, Jogulamba Temple]
-
A.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
B.
religiousTextAssociationNearby
Indicates a spatial relationship where a religious text or related object is located close to or in the immediate vicinity of another entity.
-
C.
nearbyRoyalSite
Indicates that one place or object is located close to a site associated with royalty, such as a palace, castle, or royal residence.
-
D.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
E.
hasNearbyShrine
chosen
Indicates that one entity is located close to or in the vicinity of a shrine associated with another 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 1, 2026, 1:18 a.m.