Triple
T21479071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girnar ropeway |
E529938
|
entity |
| Predicate | upperTerminalElevation |
P102982
|
FINISHED |
| Object | around 900 m above sea level |
—
|
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: around 900 m above sea level | Statement: [Girnar ropeway, upperTerminalElevation, around 900 m above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperTerminalElevation Context triple: [Girnar ropeway, upperTerminalElevation, around 900 m above sea level]
-
A.
upperStationElevation
chosen
Indicates the elevation or height above a reference level (e.g., sea level) of the upper station in a system or structure.
-
B.
elevationRangeUpperBound
Indicates the maximum elevation value that bounds the upper limit of an elevation range for something.
-
C.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
endElevation
Indicates the elevation or vertical position at which something finishes, terminates, or reaches its endpoint.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1a37a88190845810cbcacbad65 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:20 p.m.