Triple
T13950988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemiatycze |
E335521
|
entity |
| Predicate | distanceToRegionalCapitalApproximate |
P10889
|
FINISHED |
| Object | about 80–90 km south of Białystok |
—
|
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: about 80–90 km south of Białystok | Statement: [Siemiatycze, distanceToRegionalCapitalApproximate, about 80–90 km south of Białystok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRegionalCapitalApproximate Context triple: [Siemiatycze, distanceToRegionalCapitalApproximate, about 80–90 km south of Białystok]
-
A.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
distanceToDepartmentCapital
Indicates the measured distance between a given location and the capital city of its corresponding department.
-
C.
hasCountyCapitalDistance
Indicates a distance relationship specifying how far a county is from its capital.
-
D.
districtHeadquartersDistance
Indicates the distance between a place and its corresponding district headquarters.
-
E.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e131c608190b4ffdbada24a3208 |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.