Triple
T13895228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaleswari Temple |
E334069
|
entity |
| Predicate | mainShrineOrientation |
P111924
|
FINISHED |
| Object | east-facing sanctum |
—
|
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: east-facing sanctum | Statement: [Samaleswari Temple, mainShrineOrientation, east-facing sanctum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainShrineOrientation Context triple: [Samaleswari Temple, mainShrineOrientation, east-facing sanctum]
-
A.
hasGoddessShrineOrientation
Indicates the directional orientation or alignment of a shrine dedicated to a goddess in relation to a reference point or axis.
-
B.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
-
C.
majorShrineLocation
Indicates that a major religious shrine is located at or associated with a particular place or geographic location.
-
D.
mainStatueOrientation
Indicates the directional orientation or facing of the primary statue in a given context or setting.
-
E.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
- F. None of above. chosen
Provenance (4 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a741908190bdf46d76c5f1411a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:15 p.m.