Triple
T26125953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pancha Bhoota Stalas region |
E659104
|
entity |
| Predicate | hasTempleForElement |
P168048
|
FINISHED |
| Object | Ekambareswarar Temple – earth |
—
|
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: Ekambareswarar Temple – earth | Statement: [Pancha Bhoota Stalas region, hasTempleForElement, Ekambareswarar Temple – earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleForElement Context triple: [Pancha Bhoota Stalas region, hasTempleForElement, Ekambareswarar Temple – earth]
-
A.
hasComponentTemple
Indicates that an entity includes a temple as one of its constituent parts or substructures.
-
B.
hasTempleTree
Indicates that a location or entity possesses or contains a temple-associated tree.
-
C.
hasTempleFeature
Indicates that an entity possesses a specific architectural or structural feature characteristic of a temple.
-
D.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
E.
hasTempleCode
Indicates that an entity is associated with a specific temple identification code.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 26, 2026, 8:11 p.m.