Triple
T21035866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewin Kłodzki |
E518187
|
entity |
| Predicate | voivodeshipRoad |
P25639
|
FINISHED |
| Object | DW389 |
—
|
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: DW389 | Statement: [Lewin Kłodzki, voivodeshipRoad, DW389]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voivodeshipRoad Context triple: [Lewin Kłodzki, voivodeshipRoad, DW389]
-
A.
hasVoivodeshipRoad
chosen
Indicates that an entity is connected to or served by a specific voivodeship (regional) road.
-
B.
flowsThroughVoivodeship
Indicates that something, typically a river or waterway, passes through or traverses the territory of a specified voivodeship (administrative region).
-
C.
hasCountyRoad
Indicates that one place or administrative area is connected to or served by a designated county-maintained road.
-
D.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
E.
associatedVoivodeship
Indicates that one entity is administratively or geographically linked to a specific voivodeship (province-level region).
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc865ca88190abf336ee9012fa77 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:02 p.m.