Triple
T27616488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Valley region |
E700450
|
entity |
| Predicate | adjacentToMountainRange |
P100660
|
FINISHED |
| Object | Wasatch Range |
—
|
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: Wasatch Range | Statement: [Utah Valley region, adjacentToMountainRange, Wasatch Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentToMountainRange Context triple: [Utah Valley region, adjacentToMountainRange, Wasatch Range]
-
A.
adjacentMountain
Indicates that one mountain is directly next to or touching another mountain, with no significant separation between them.
-
B.
locatedInMountainRangeRegion
Indicates that a place or geographic entity is situated within the area covered by a specific mountain range.
-
C.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
D.
nearbyMountainRegion
chosen
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
-
E.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 2:12 p.m.