Triple
T27697304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meenakshi shrine |
E698332
|
entity |
| Predicate | centralSanctumOf |
P65786
|
FINISHED |
| Object | Meenakshi Amman 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: Meenakshi Amman Temple | Statement: [Meenakshi shrine, centralSanctumOf, Meenakshi Amman Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralSanctumOf Context triple: [Meenakshi shrine, centralSanctumOf, Meenakshi Amman Temple]
-
A.
sanctumContains
Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
-
B.
otherRelatedSanctums
Indicates that there exist additional sanctums that are related or connected to a given sanctum in some relevant way.
-
C.
hasMainSanctum
chosen
Indicates that an entity possesses a primary or central sacred space used for core religious or spiritual activities.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
centralCeremonyLocation
Indicates the place that serves as the primary or focal site where a ceremony is held.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 2:55 p.m.