Triple
T36047271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowe Miasto nad Pilicą |
E1042705
|
entity |
| Predicate | distanceToGrójec |
P204711
|
FINISHED |
| Object | about 34 km |
—
|
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 34 km | Statement: [Nowe Miasto nad Pilicą, distanceToGrójec, about 34 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGrójec Context triple: [Nowe Miasto nad Pilicą, distanceToGrójec, about 34 km]
-
A.
distanceToElbląg_km
Indicates the physical distance, measured in kilometers, between an entity and the location Elbląg.
-
B.
distanceToPoznań_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Poznań.
-
C.
distanceToWrocławApproxKm
Indicates an approximate distance, measured in kilometers, between an entity and the city of Wrocław.
-
D.
distanceToKraków_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Kraków.
-
E.
distanceToBydgoszcz
Indicates the spatial distance between a given place or object and the city of Bydgoszcz.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.