Triple
T35890834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamundeshwari |
E1037775
|
entity |
| Predicate | templeElevation |
P95312
|
FINISHED |
| Object | Chamundi Hills |
—
|
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: Chamundi Hills | Statement: [Chamundeshwari, templeElevation, Chamundi Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeElevation Context triple: [Chamundeshwari, templeElevation, Chamundi Hills]
-
A.
templeDimensions
Indicates the measured size or proportions of a temple, such as its length, width, height, or overall spatial layout.
-
B.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
C.
templeComplexLevel
Indicates the hierarchical level or rank of a temple within a larger temple complex or religious site structure.
-
D.
hillTemple
chosen
Indicates a relationship where a temple is located on, associated with, or dedicated to a hill.
-
E.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3a7d0881909bcd9f04a8189ee9 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.