Triple
T21959318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandimandir |
E542280
|
entity |
| Predicate | proximityToHills |
P39023
|
FINISHED |
| Object | near Shivalik foothills |
—
|
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: near Shivalik foothills | Statement: [Chandimandir, proximityToHills, near Shivalik foothills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToHills Context triple: [Chandimandir, proximityToHills, near Shivalik foothills]
-
A.
hasNearbyHills
Indicates that one location or area is situated close to one or more hills.
-
B.
hasNearbyHillRange
chosen
Indicates that one entity is located close to or within the vicinity of a range of hills associated with the other entity.
-
C.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
D.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
E.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12454a290819094d4b56547816e3f |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8 p.m.