Triple
T34424974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gangolli |
E883641
|
entity |
| Predicate | nearbyPilgrimageCenter |
P61457
|
FINISHED |
| Object | Kollur Mookambika 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: Kollur Mookambika Temple | Statement: [Gangolli, nearbyPilgrimageCenter, Kollur Mookambika Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPilgrimageCenter Context triple: [Gangolli, nearbyPilgrimageCenter, Kollur Mookambika Temple]
-
A.
hasNearbyPilgrimageSite
chosen
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
B.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
C.
nearbyGhats
Indicates that one location is situated close to or in the immediate vicinity of a ghat (such as a riverfront or stepped embankment).
-
D.
nearbyRoyalSite
Indicates that one place or object is located close to a site associated with royalty, such as a palace, castle, or royal residence.
-
E.
nearbyHeritageDestinations
Indicates that one or more heritage destinations are located close to a given reference point or entity in geographic space.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 1, 2026, 2 a.m.