Triple
T17846898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sułoszowa |
E445686
|
entity |
| Predicate | hasNotableUrbanForm |
P90675
|
FINISHED |
| Object | one-street village |
—
|
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: one-street village | Statement: [Sułoszowa, hasNotableUrbanForm, one-street village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableUrbanForm Context triple: [Sułoszowa, hasNotableUrbanForm, one-street village]
-
A.
containsUrbanForm
Indicates that one entity spatially includes or encompasses an urban form or built-up area within its extent.
-
B.
hasPlannedUrbanCharacter
Indicates that an area exhibits an intentionally designed and organized urban form, layout, and land use pattern rather than informal or unplanned development.
-
C.
hasUrbanFeature
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
-
D.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
-
E.
hasUrbanLayoutType
chosen
Indicates that an entity possesses or is characterized by a specific type or pattern of urban spatial layout.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffb35248190a80a428686e06d87 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.