Triple
T27056850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manebhanjan–Sandakphu route |
E684919
|
entity |
| Predicate | hasEndPointElevation |
P47741
|
FINISHED |
| Object | approximately 3636 metres |
—
|
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: approximately 3636 metres | Statement: [Manebhanjan–Sandakphu route, hasEndPointElevation, approximately 3636 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndPointElevation Context triple: [Manebhanjan–Sandakphu route, hasEndPointElevation, approximately 3636 metres]
-
A.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
B.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
C.
hasViewpointElevation
Indicates the vertical height or altitude of the viewpoint relative to a reference level (such as ground or sea level).
-
D.
endElevation
chosen
Indicates the elevation or vertical position at which something finishes, terminates, or reaches its endpoint.
-
E.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 8:18 a.m.