Triple
T27713646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nose |
E698757
|
entity |
| Predicate | relativeLocationOnMountain |
P73665
|
FINISHED |
| Object | eastern side of Mount Mansfield ridge |
—
|
LITERAL 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: eastern side of Mount Mansfield ridge | Statement: [The Nose, relativeLocationOnMountain, eastern side of Mount Mansfield ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationOnMountain Context triple: [The Nose, relativeLocationOnMountain, eastern side of Mount Mansfield ridge]
-
A.
positionRelativeToSummit
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
B.
sideOfMountain
chosen
Indicates that one entity is located on or corresponds to a particular side or face of a mountain relative to another entity.
-
C.
locatedOnPeak
Indicates that one entity is situated at or on the summit or highest point of another entity (a peak).
-
D.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
E.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: April 27, 2026, 3:03 p.m.