Triple
T27850666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daman-e-Koh |
E703941
|
entity |
| Predicate | elevationAboveIslamabad_m |
P171774
|
FINISHED |
| Object | approximately 300 to 500 |
—
|
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: approximately 300 to 500 | Statement: [Daman-e-Koh, elevationAboveIslamabad_m, approximately 300 to 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationAboveIslamabad_m Context triple: [Daman-e-Koh, elevationAboveIslamabad_m, approximately 300 to 500]
-
A.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
-
B.
elevationRelativeToKhumbu
Indicates the relative elevation of one location compared to the Khumbu region, expressing how much higher or lower it is.
-
C.
mountainHeight
Indicates the vertical elevation or height of a mountain, typically measured from sea level.
-
D.
distanceFromMuzaffarabad_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Muzaffarabad.
-
E.
distanceFromShimla_km
Indicates the physical distance, measured in kilometers, between a given place and Shimla.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 27, 2026, 6:10 p.m.