Triple
T17814521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alay Valley |
E444801
|
entity |
| Predicate | highestSurroundingPeaks |
P129006
|
FINISHED |
| Object | over 7000 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: over 7000 metres | Statement: [Alay Valley, highestSurroundingPeaks, over 7000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestSurroundingPeaks Context triple: [Alay Valley, highestSurroundingPeaks, over 7000 metres]
-
A.
highestPeaksRelativeTo
Indicates a relationship where one location or region is associated with the tallest mountain peaks it contains, relative to surrounding areas or a defined reference set.
-
B.
nearestHigherPeak
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
-
C.
hasHigherPeaksNearby
Indicates that an entity is located near other entities whose peak elevations are higher than its own.
-
D.
highestPeaksLocatedIn
Indicates that the specified highest mountain peaks are geographically situated within the given location or region.
-
E.
highestNearbyPeakElevationInFeet
Indicates the elevation in feet of the tallest peak located within a defined nearby area of a given reference point.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887e80688190a2ac3308b0e815c6 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:14 a.m.