Triple
T13122144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamrud Fort |
E311749
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Jamrud |
E266758
|
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: Jamrud | Statement: [Jamrud Fort, locatedIn, Jamrud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jamrud Context triple: [Jamrud Fort, locatedIn, 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.
Khuzhir
Khuzhir is the main village and tourist hub on Olkhon Island in Lake Baikal, Russia, known for its proximity to the sacred Shaman Rock and dramatic Siberian landscapes.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819840b881909b76022b4c4dcaed |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e289462c8190b1625a26f019d744 |
completed | May 3, 2026, 5:52 a.m. |
Created at: April 9, 2026, 9:06 p.m.