Triple
T19522981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sad-bhawna Shikhar |
E488449
|
entity |
| Predicate | hasElevationRank |
P136632
|
FINISHED |
| Object | highest peak of the Vindhya Range |
—
|
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: highest peak of the Vindhya Range | Statement: [Sad-bhawna Shikhar, hasElevationRank, highest peak of the Vindhya Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationRank Context triple: [Sad-bhawna Shikhar, hasElevationRank, highest peak of the Vindhya Range]
-
A.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
B.
post-elevationRank
Indicates that one entity holds a higher or later elevation-based rank or status than another entity.
-
C.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
D.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
E.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e635a1ae9881908dfdcc94490c57aa |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.