Triple
T12419023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith Creek |
E296715
|
entity |
| Predicate | rangeContext |
P32691
|
FINISHED |
| Object | eastern Nevada mountain range |
—
|
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 Nevada mountain range | Statement: [Smith Creek, rangeContext, eastern Nevada mountain range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeContext Context triple: [Smith Creek, rangeContext, eastern Nevada mountain range]
-
A.
regionContext
chosen
Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
-
B.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
C.
rangeState
Indicates that an entity’s state or condition falls within a specified range or interval.
-
D.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
-
E.
rangeBehavior
Indicates how an entity behaves or operates when interacting with or within a specified range or distance.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.