Triple
T34698445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic street network of Goslar |
E891096
|
entity |
| Predicate | urbanFormType |
P180110
|
FINISHED |
| Object | medieval core |
—
|
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: medieval core | Statement: [historic street network of Goslar, urbanFormType, medieval core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanFormType Context triple: [historic street network of Goslar, urbanFormType, medieval core]
-
A.
urbanPlanningForm
Indicates the specific type or structure of urban planning approach applied to a place or development.
-
B.
urbanSectionType
Indicates the specific category or type of an urban section within a city or built environment (e.g., residential, commercial, industrial).
-
C.
urbanDevelopmentType
Indicates the specific category or nature of urban development associated with or applied to an entity (e.g., residential, commercial, mixed-use).
-
D.
urbanDesignType
Indicates the specific category or style of urban design that characterizes or is applied to a place or project.
-
E.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
- F. None of above. chosen
Provenance (4 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f731cbca10819091eefe2f2487928e |
completed | May 3, 2026, 11:30 a.m. |
Created at: May 1, 2026, 2:05 a.m.