Triple
T9189628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zalewo |
E220547
|
entity |
| Predicate | distanceToIława |
P86724
|
FINISHED |
| Object | approximately 28 km north |
—
|
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: approximately 28 km north | Statement: [Zalewo, distanceToIława, approximately 28 km north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToIława Context triple: [Zalewo, distanceToIława, approximately 28 km north]
-
A.
distanceToKraków_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Kraków.
-
B.
distanceToKielce
Indicates the spatial distance between a given entity and the city of Kielce.
-
C.
distanceFromTarnów
Indicates the measured spatial distance between a given location and the city of Tarnów.
-
D.
distanceToWarsaw
Indicates the spatial distance between a given entity’s location and the city of Warsaw.
-
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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5bd8c5c81909d0cdbcd7410fcee |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:24 p.m.