Triple
T35315625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldier Mountains (Idaho) |
E1019896
|
entity |
| Predicate | neighboringRange |
P75455
|
FINISHED |
| Object | Smoky Mountains (Idaho) |
—
|
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: Smoky Mountains (Idaho) | Statement: [Soldier Mountains (Idaho), neighboringRange, Smoky Mountains (Idaho)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringRange Context triple: [Soldier Mountains (Idaho), neighboringRange, Smoky Mountains (Idaho)]
-
A.
neighboringRegion
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
B.
neighboringTo
chosen
Indicates that one entity is located directly adjacent or very close to another entity, sharing a common boundary or immediate vicinity.
-
C.
associatedRange
Indicates that one entity is linked to or falls within a particular range defined or referenced by another entity.
-
D.
neighboringBlockNext
Indicates that one block is directly adjacent to and immediately follows another block in the spatial or ordered layout.
-
E.
neighboringProvision
Indicates that one entity provides resources, services, or support to another entity located nearby or in an adjacent area.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.