Triple
T27696618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lal Pur District |
E698311
|
entity |
| Predicate | borderingAreaAcrossBorder |
P224
|
FINISHED |
| Object | Khyber District |
—
|
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: Khyber District | Statement: [Lal Pur District, borderingAreaAcrossBorder, Khyber District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingAreaAcrossBorder Context triple: [Lal Pur District, borderingAreaAcrossBorder, Khyber District]
-
A.
borderTownAcrossBorder
Indicates that a town lies on one side of a border directly opposite or adjacent to a town on the other side of that border.
-
B.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
C.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
D.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 2:54 p.m.