Triple
T16560483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Śródmieście, Łódź |
E402323
|
entity |
| Predicate | streetNetworkPattern |
P3374
|
FINISHED |
| Object | grid-like |
—
|
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: grid-like | Statement: [Śródmieście, Łódź, streetNetworkPattern, grid-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNetworkPattern Context triple: [Śródmieście, Łódź, streetNetworkPattern, grid-like]
-
A.
streetNetwork
chosen
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
B.
streetNetworkIncludes
Indicates that a given street network contains or encompasses a specified street segment, feature, or component as part of its structure.
-
C.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
D.
hasStreetNamingPattern
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
E.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576d88288190b33543bea4706a36 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.