Triple
T37326816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komalavalli Thayar shrine |
E926626
|
entity |
| Predicate | orientationWithinTemple |
P187730
|
FINISHED |
| Object | within main temple complex of Sarangapani Temple |
—
|
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: within main temple complex of Sarangapani Temple | Statement: [Komalavalli Thayar shrine, orientationWithinTemple, within main temple complex of Sarangapani Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationWithinTemple Context triple: [Komalavalli Thayar shrine, orientationWithinTemple, within main temple complex of Sarangapani Temple]
-
A.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
B.
residesInTemple
Indicates that one entity lives or dwells within a temple associated with another entity.
-
C.
templeAccess
Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
-
D.
roleAtTemple
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
-
E.
mainShrineOrientation
Indicates the directional alignment or facing direction of a main shrine relative to a reference point or axis.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:16 p.m.