Triple
T2440309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peshawar |
E53256
|
entity |
| Predicate | borderTradeRole |
P10963
|
FINISHED |
| Object | gateway to Afghanistan |
—
|
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: gateway to Afghanistan | Statement: [Peshawar, borderTradeRole, gateway to Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTradeRole Context triple: [Peshawar, borderTradeRole, gateway to Afghanistan]
-
A.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
B.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
C.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
D.
hasBorderCrossingFunction
chosen
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
E.
nearBorderCrossing
Indicates that an entity is located close to a border crossing point between two regions or countries.
- F. None of above.
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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.