Triple
T25961686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhilandeswari shrine |
E645554
|
entity |
| Predicate | isProminentSanctumWithin |
P65786
|
FINISHED |
| Object | Jambukeswarar 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: Jambukeswarar Temple | Statement: [Akhilandeswari shrine, isProminentSanctumWithin, Jambukeswarar Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProminentSanctumWithin Context triple: [Akhilandeswari shrine, isProminentSanctumWithin, Jambukeswarar Temple]
-
A.
hasMainSanctum
chosen
Indicates that an entity possesses a primary or central sacred space used for core religious or spiritual activities.
-
B.
isInSanctuaryWith
Indicates that two or more entities are located together within the same sanctuary or protected refuge at the same time.
-
C.
hasMainSanctumOrientation
Indicates the primary directional orientation of a structure’s main sanctum relative to a reference frame (e.g., cardinal directions).
-
D.
sanctumContains
Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
-
E.
hasNearbySanctuary
Indicates that one entity has a sanctuary or place of refuge located close to it in space or distance.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 8:47 a.m.