Triple
T24485669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS Explorer 455 |
E617498
|
entity |
| Predicate | notablePeakCovered |
P20909
|
FINISHED |
| Object | Clisham |
—
|
NE NERFINISHED |
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: Clisham | Statement: [OS Explorer 455, notablePeakCovered, Clisham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeakCovered Context triple: [OS Explorer 455, notablePeakCovered, Clisham]
-
A.
notablePeak
chosen
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
B.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
C.
notableClimbs
Indicates that the subject has completed or is associated with particularly significant or well-known climbing routes or ascents.
-
D.
isOneOfHighestPeaksIn
Indicates that an entity is among the tallest or most elevated peaks within a specified group, region, or category.
-
E.
otherMajorPeak
Indicates that one peak is another significant or prominent peak associated with, but distinct from, a given primary peak.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:21 a.m.