Triple
T29591272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donaldson Mountain |
E754165
|
entity |
| Predicate | isOnRidgeWith |
P167487
|
FINISHED |
| Object | Seward 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: Seward Mountain | Statement: [Donaldson Mountain, isOnRidgeWith, Seward Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRidgeWith Context triple: [Donaldson Mountain, isOnRidgeWith, Seward Mountain]
-
A.
isOnRidgeBetween
Indicates that something is located on the ridge that lies between two other reference points or areas.
-
B.
isRidge
Indicates that something has the form or function of a ridge, typically being a long, narrow raised or elevated feature relative to its surroundings.
-
C.
hasRidgeRoute
Indicates that one entity possesses or is associated with a route that follows or traverses a ridge.
-
D.
isOnSlopeOf
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or structure.
-
E.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66db3419081908757734f62faf927 |
completed | May 2, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:14 p.m.