Triple
T27697319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meenakshi shrine |
E698332
|
entity |
| Predicate | associatedWithConsortShrine |
P27875
|
FINISHED |
| Object | Sundareswarar shrine |
—
|
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: Sundareswarar shrine | Statement: [Meenakshi shrine, associatedWithConsortShrine, Sundareswarar shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithConsortShrine Context triple: [Meenakshi shrine, associatedWithConsortShrine, Sundareswarar shrine]
-
A.
associatedShrine
chosen
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
B.
associatedShrineComplex
Indicates that one entity is linked or connected to a particular shrine complex, typically through location, function, or religious association.
-
C.
associatedWithTempleTown
Indicates a relationship where an entity has a connection or linkage to a town that is characterized by or centered around a temple.
-
D.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
E.
associatedWithTempleComplex
Indicates a relationship in which an entity is connected or related to a specific temple complex, such as by location, function, use, or historical association.
- 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_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: April 27, 2026, 2:55 p.m.