Triple
T25115320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quetta–Chaman corridor |
E629110
|
entity |
| Predicate | linkedBorderTown |
P107933
|
FINISHED |
| Object | Chaman |
—
|
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: Chaman | Statement: [Quetta–Chaman corridor, linkedBorderTown, Chaman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedBorderTown Context triple: [Quetta–Chaman corridor, linkedBorderTown, Chaman]
-
A.
isBorderTownBetween
Indicates that a town is located on or near the boundary separating two specified regions, serving as a border settlement between them.
-
B.
borderTownAcrossBorder
chosen
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.
-
C.
hasBorderTownOnCanadianSide
Indicates that one location has a corresponding border town situated on the Canadian side of an international boundary.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
borderStreet
Indicates that a street forms or lies along the boundary between two geographic areas or properties.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 6:27 a.m.