Triple
T17826851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabierzów |
E445139
|
entity |
| Predicate | geographicRelationToKraków |
P129348
|
FINISHED |
| Object | north-west of Kraków |
—
|
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: north-west of Kraków | Statement: [Zabierzów, geographicRelationToKraków, north-west of Kraków]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicRelationToKraków Context triple: [Zabierzów, geographicRelationToKraków, north-west of Kraków]
-
A.
distanceToKraków_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Kraków.
-
B.
associatedWithVoivodeshipCapital
Indicates a relationship where something is linked or connected to the capital city of a voivodeship (a regional administrative unit).
-
C.
distanceToPoznań_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Poznań.
-
D.
distanceToKatowice
Indicates the spatial distance between a given entity and the city of Katowice.
-
E.
distanceToWrocławApproxKm
Indicates an approximate distance, measured in kilometers, between an entity and the city of Wrocław.
- F. None of above. chosen
Provenance (4 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48914e20481908883d1da194f446c |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:15 a.m.