Triple
T27385917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Shoshone Peak |
E691371
|
entity |
| Predicate | inMountainSystem |
P648
|
FINISHED |
| Object | Great Basin mountain ranges |
—
|
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: Great Basin mountain ranges | Statement: [North Shoshone Peak, inMountainSystem, Great Basin mountain ranges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inMountainSystem Context triple: [North Shoshone Peak, inMountainSystem, Great Basin mountain ranges]
-
A.
mountainSystem
Indicates a relationship where multiple mountains are grouped together as part of the same connected or coherent mountain system or range.
-
B.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain range.
-
C.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
-
D.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
E.
mountainRange
chosen
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c8af8508190bf5e40515d5d8f34 |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:24 p.m.