Triple

T17419030
Position Surface form Disambiguated ID Type / Status
Subject Battle of Jamrud E423560 entity
Predicate location P40 FINISHED
Object Jamrud NE NERFINISHED

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: Jamrud | Statement: [Battle of Jamrud, location, Jamrud]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jamrud
Context triple: [Battle of Jamrud, location, Jamrud]
  • A. Jamrud chosen
    Jamrud is a strategically important town in Pakistan’s Khyber District, historically serving as a gateway to the Khyber Pass and a key military and trade outpost.
  • B. Samalkha
    Samalkha is a town in the northern Indian state of Haryana, known for its industrial activity and location along major transport routes.
  • C. Rajadell
    Rajadell is a small rural municipality in the comarca of Bages in Catalonia, Spain.
  • D. Mogh
    Mogh is a Klingon warrior of the House of Mogh in the Star Trek universe, best known as the father of Worf.
  • E. Dunyazad
    Dunyazad is a character in the collection of Middle Eastern folk tales known as One Thousand and One Nights, traditionally depicted as the younger sister of Scheherazade.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44234d840819096484a15d407785a completed April 19, 2026, 2:47 a.m.
Created at: April 10, 2026, 5:46 a.m.