Triple
T18361871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catskill 3500 Club peaks |
E439936
|
entity |
| Predicate | notableHighestPeak |
P28959
|
FINISHED |
| Object | Slide Mountain |
—
|
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: Slide Mountain | Statement: [Catskill 3500 Club peaks, notableHighestPeak, Slide Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHighestPeak Context triple: [Catskill 3500 Club peaks, notableHighestPeak, Slide Mountain]
-
A.
notablePeak
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
B.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
C.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
-
D.
countryHighestPointAccess
Indicates that an entity has access to, or the ability to reach or utilize, the highest geographical point within a specified country.
-
E.
territorialPeak
chosen
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516dbd4748190a6c5715ef943bd4a |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.