Triple
T20303524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maihar Devi Temple |
E505545
|
entity |
| Predicate | ropewayPurpose |
P127558
|
FINISHED |
| Object | facilitates access to hilltop shrine |
—
|
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: facilitates access to hilltop shrine | Statement: [Maihar Devi Temple, ropewayPurpose, facilitates access to hilltop shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ropewayPurpose Context triple: [Maihar Devi Temple, ropewayPurpose, facilitates access to hilltop shrine]
-
A.
ropewayConnects
Indicates that a ropeway (such as a cable car or gondola system) provides a direct transportation connection between two locations.
-
B.
ropewayName
Indicates the name assigned to a ropeway (such as a cable car or aerial lift) associated with the subject.
-
C.
routePurpose
chosen
Indicates the intended function or goal that a particular route is designed or used to serve.
-
D.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
E.
tollPurpose
Indicates that a toll is imposed for a specific purpose, such as funding, maintenance, or use of a particular facility or service.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773e0864819095d272659cd2074d |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:17 a.m.