Triple
T12075169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latok I |
E287525
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Latok IV |
E295878
|
NE 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: Latok IV | Statement: [Latok I, near, Latok IV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Latok IV Context triple: [Latok I, near, Latok IV]
-
A.
Latok IV
chosen
Latok IV is a lesser-known but formidable granite peak in the Latok group of the Karakoram range in Pakistan, popular among elite alpinists for its challenging, rarely climbed routes.
-
B.
Latok III
Latok III is a prominent granite peak in the Latok group of the Karakoram range in Pakistan, known for its steep faces and challenging mountaineering routes.
-
C.
Latok II
Latok II is a prominent, steep granite peak in the Latok group of the Karakoram range in Pakistan, renowned among alpinists for its challenging technical routes and remote location.
-
D.
Latok I
Latok I is a prominent and notoriously difficult-to-climb granite peak in the Karakoram range of Pakistan.
-
E.
Lohapol
Lohapol is one of the historic entrance gates of Mehrangarh Fort in Jodhpur, Rajasthan, known for its massive iron-studded doors and memorial handprints of royal widows.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9045bbc508190abf6e3316701e587 |
completed | April 10, 2026, 2:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f655551d8c81909bf0980951f10320 |
completed | May 2, 2026, 7:49 p.m. |
Created at: April 8, 2026, 9:48 p.m.