Triple
T28114532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiva as Pateeswarar |
E710583
|
entity |
| Predicate | hasPrimaryShrineLocation |
P21389
|
FINISHED |
| Object | garbhagriha of Perur Pateeswarar 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: garbhagriha of Perur Pateeswarar Temple | Statement: [Shiva as Pateeswarar, hasPrimaryShrineLocation, garbhagriha of Perur Pateeswarar Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryShrineLocation Context triple: [Shiva as Pateeswarar, hasPrimaryShrineLocation, garbhagriha of Perur Pateeswarar Temple]
-
A.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
B.
hasMainShrineMaterial
Indicates the primary material from which a shrine is constructed or predominantly made.
-
C.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
D.
hasMajorShrine
chosen
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
E.
containsShrine
Indicates that one entity includes or has within its boundaries a shrine associated with it.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: April 27, 2026, 9:13 p.m.