Triple

T14005450
Position Surface form Disambiguated ID Type / Status
Subject Pindi Point E336934 entity
Predicate near P350 FINISHED
Object Kashmir Point E334082 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: Kashmir Point | Statement: [Pindi Point, near, Kashmir Point]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kashmir Point
Context triple: [Pindi Point, near, Kashmir Point]
  • A. Kashmir Point chosen
    Kashmir Point is a popular scenic viewpoint in Murree, Pakistan, known for its panoramic vistas of the surrounding hills and, on clear days, distant views of the Kashmir mountains.
  • B. Kohima Bench
    The Kohima Bench is a regional branch of the Gauhati High Court that exercises judicial authority over the state of Nagaland in India.
  • C. Chak Fort
    Chak Fort is an alternative name for the historic Red Fort located in Muzaffarabad, in the Azad Jammu and Kashmir region of Pakistan.
  • D. Daulat Beg Oldi
    Daulat Beg Oldi is a high-altitude military outpost and airstrip in the Ladakh region of India, near the Line of Actual Control with China.
  • E. Hill 395
    Hill 395, also known as White Horse Hill, is a strategically important elevation in Korea that was the focal point of intense fighting during the Korean War.
  • 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_69d81c645c5c8190b1fd16a285a1b78a completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ed1d2548190bb46d6b7cba4ffde completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbaca41d24819086df2329ea3c4c9c completed May 6, 2026, 9:03 p.m.
Created at: April 9, 2026, 10:19 p.m.