Triple
T26903987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jambukeswarar Temple |
E678101
|
entity |
| Predicate | sanctumFeature |
P132141
|
FINISHED |
| Object | natural spring under the lingam |
—
|
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: natural spring under the lingam | Statement: [Jambukeswarar Temple, sanctumFeature, natural spring under the lingam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctumFeature Context triple: [Jambukeswarar Temple, sanctumFeature, natural spring under the lingam]
-
A.
sanctumContains
chosen
Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
-
B.
hasMainSanctum
Indicates that an entity possesses a primary or central sacred space used for core religious or spiritual activities.
-
C.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
D.
otherRelatedSanctums
Indicates that there exist additional sanctums that are related or connected to a given sanctum in some relevant way.
-
E.
oneOfMultipleSanctums
Indicates that an entity is one among several sanctums associated with or available to 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:52 a.m.