Triple
T24198109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Peak of Mount Foraker |
E599889
|
entity |
| Predicate | hasPrimarySummit |
P155148
|
FINISHED |
| Object | South Peak of Mount Foraker |
—
|
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: South Peak of Mount Foraker | Statement: [North Peak of Mount Foraker, hasPrimarySummit, South Peak of Mount Foraker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySummit Context triple: [North Peak of Mount Foraker, hasPrimarySummit, South Peak of Mount Foraker]
-
A.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
B.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
C.
hasHigherSummit
Indicates that one entity’s summit is higher in elevation than another entity’s summit.
-
D.
hasSummitFeature
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
E.
hasSummitMarker
Indicates that a location or peak is marked by an official summit marker or sign denoting its highest 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.