Triple
T38246989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hummanaya Blowhole |
E1013916
|
entity |
| Predicate | distanceFromDikwella |
P204567
|
FINISHED |
| Object | about 6–7 kilometres |
—
|
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: about 6–7 kilometres | Statement: [Hummanaya Blowhole, distanceFromDikwella, about 6–7 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDikwella Context triple: [Hummanaya Blowhole, distanceFromDikwella, about 6–7 kilometres]
-
A.
distanceFromGuwahati_km
Indicates the physical distance, measured in kilometers, between an entity and the location of Guwahati.
-
B.
distanceFromKathmandu
Indicates the measured spatial distance between a given location or entity and the city of Kathmandu.
-
C.
distanceToThimphu
Indicates the measured spatial distance between a given entity’s location and the city of Thimphu.
-
D.
distanceToNepalgunj_km
Indicates the physical distance, measured in kilometers, between a given location and Nepalgunj.
-
E.
distanceFromKullu
Indicates the spatial distance measured from the reference location Kullu to another place or entity.
- F. None of above. chosen
Provenance (4 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.