Triple
T19329633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maihar |
E483450
|
entity |
| Predicate | templeAccess |
P135442
|
FINISHED |
| Object | reachable by steps and ropeway (cable car) |
—
|
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: reachable by steps and ropeway (cable car) | Statement: [Maihar, templeAccess, reachable by steps and ropeway (cable car)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeAccess Context triple: [Maihar, templeAccess, reachable by steps and ropeway (cable car)]
-
A.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
-
B.
isActiveTemple
Indicates that a temple is currently functioning and in regular religious use, rather than being abandoned, ruined, or inactive.
-
C.
templePractice
Indicates a religious or ritual activity that is performed within or in connection with a temple.
-
D.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
E.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6163ffddc81909e9cb13e780f1f18 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:33 p.m.