Triple
T21345445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamirpur district |
E526320
|
entity |
| Predicate | hasHillRanges |
P651
|
FINISHED |
| Object | lower Himalayan ranges |
—
|
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: lower Himalayan ranges | Statement: [Hamirpur district, hasHillRanges, lower Himalayan ranges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHillRanges Context triple: [Hamirpur district, hasHillRanges, lower Himalayan ranges]
-
A.
hasMountainRange
chosen
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
B.
hasNotableHillRange
Indicates that an entity possesses or is associated with a significant or well-known range of hills.
-
C.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
-
D.
hasNearbyHillRange
Indicates that one entity is located close to or within the vicinity of a range of hills associated with the other entity.
-
E.
hasHillSize
Indicates that something possesses or is characterized by a particular hill size.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a854e8ec81909efd41c1e959cc61 |
completed | April 22, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:54 p.m.