Triple
T20810180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zduńska Wola County |
E512275
|
entity |
| Predicate | transportNetworkFeature |
P56025
|
FINISHED |
| Object | road connections to Łódź |
—
|
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: road connections to Łódź | Statement: [Zduńska Wola County, transportNetworkFeature, road connections to Łódź]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportNetworkFeature Context triple: [Zduńska Wola County, transportNetworkFeature, road connections to Łódź]
-
A.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
B.
transportNetworkPartOf
Indicates that one transport network is a component or subdivision of a larger, encompassing transport network.
-
C.
shareTransportInfrastructure
Indicates that multiple entities make joint use of the same transport infrastructure facilities or systems.
-
D.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
E.
typeOfTransportInfrastructure
chosen
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d27a4881908b34679385d8b94b |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.