Triple
T17236893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beschryvinge der stad Delft |
E418386
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | topographical description |
C15174
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: topographical description Context triple: [Beschryvinge der stad Delft, instanceOf, topographical description]
-
A.
topographical model
chosen
A topographical model is a conceptual representation that maps the spatial features and relationships of a terrain or surface, often including elevation, contours, and physical landmarks.
-
B.
geographical feature
A geographical feature is a naturally occurring or human-made physical element of the Earth's surface, such as mountains, rivers, valleys, or roads, that can be distinctly identified and described.
-
C.
topographic lowland
A topographic lowland is a broad, relatively low-lying area of the Earth's surface that is lower in elevation than the surrounding terrain and often associated with plains, valleys, or basins.
-
D.
topographical feature of ancient cities
A topographical feature of ancient cities is a natural or human-modified physical element of the urban landscape—such as hills, rivers, valleys, or terraces—that shaped the city’s layout, defenses, infrastructure, and social organization.
-
E.
regional topolect
A regional topolect is a localized variety of a language spoken in a specific geographic area, characterized by distinct phonological, lexical, and grammatical features that differentiate it from other regional forms and the standard language.
- F. None of above.
Provenance (1 batch)
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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.