Triple
T25226076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quetta–Taftan Railway Line |
E632089
|
entity |
| Predicate | connectsBorderPoint |
P28958
|
FINISHED |
| Object | Taftan |
—
|
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: Taftan | Statement: [Quetta–Taftan Railway Line, connectsBorderPoint, Taftan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsBorderPoint Context triple: [Quetta–Taftan Railway Line, connectsBorderPoint, Taftan]
-
A.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
B.
connectsCountryBorder
chosen
Indicates that one entity forms a direct land or maritime border connection with a specified country.
-
C.
connectsBorderCities
Indicates a relationship where a route, infrastructure, or boundary directly links two or more cities that lie on or near a shared border.
-
D.
hasBorderConnectionPotential
Indicates that two regions or entities are positioned such that they could feasibly share a border or direct boundary under certain conditions.
-
E.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 1:03 p.m.