Triple
T35040452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarahs |
E1011054
|
entity |
| Predicate | borderPartnerCity |
P57276
|
FINISHED |
| Object | Sarakhs, Iran |
—
|
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: Sarakhs, Iran | Statement: [Sarahs, borderPartnerCity, Sarakhs, Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPartnerCity Context triple: [Sarahs, borderPartnerCity, Sarakhs, Iran]
-
A.
shareMajorBorderCities
Indicates that two regions or countries have a shared border along which there are one or more major cities situated on or near that boundary.
-
B.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative areas.
-
C.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
D.
isNeighboringCityOf
chosen
Indicates that one city is geographically adjacent to or directly borders another city.
-
E.
sisterCityCountry
Indicates that a city has an official sister-city relationship with a city located in the specified country.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: May 3, 2026, 4:01 p.m.