Triple
T36398968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titcomb Basin |
E896566
|
entity |
| Predicate | hasNotableNearbyPeak |
P7612
|
FINISHED |
| Object | Gannett Peak |
E284471
|
NE 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: Gannett Peak | Statement: [Titcomb Basin, hasNotableNearbyPeak, Gannett Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNearbyPeak Context triple: [Titcomb Basin, hasNotableNearbyPeak, Gannett Peak]
-
A.
hasHigherPeaksNearby
Indicates that an entity is located near other entities whose peak elevations are higher than its own.
-
B.
hasNearbyPeak
chosen
Indicates that one location has another peak situated close to it in geographic space.
-
C.
hasNotableNearbyMountain
Indicates that an entity is located near and is notably associated with a particular mountain.
-
D.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
E.
nearestHigherPeak
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
- F. None of above.
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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a79b1852d008190a81c5391ee2b07b3 |
completed | Aug. 10, 2026, 11:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.