Triple
T20262413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knyszyn |
E498875
|
entity |
| Predicate | distanceFromBiałystok |
P103008
|
FINISHED |
| Object | about 30 km northwest |
—
|
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 30 km northwest | Statement: [Knyszyn, distanceFromBiałystok, about 30 km northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBiałystok Context triple: [Knyszyn, distanceFromBiałystok, about 30 km northwest]
-
A.
distanceToBiałystok
chosen
Indicates the spatial distance between a given entity and the city of Białystok.
-
B.
distanceToOstróda
Indicates the spatial distance between a given entity or location and the town of Ostróda.
-
C.
distanceToGdańsk_km
Indicates the physical distance, measured in kilometers, between a given place and the city of Gdańsk.
-
D.
distanceToOlsztyn
Indicates the spatial distance between a given entity and the location of Olsztyn.
-
E.
distanceToWarsaw
Indicates the spatial distance between a given entity’s location and the city of Warsaw.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674cba2748190a886ecd8316dc518 |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.