Triple
T27484733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chełmno |
E693702
|
entity |
| Predicate | hasOldTownLayout |
P90675
|
FINISHED |
| Object | medieval grid plan |
—
|
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 grid plan | Statement: [Chełmno, hasOldTownLayout, medieval grid plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldTownLayout Context triple: [Chełmno, hasOldTownLayout, medieval grid plan]
-
A.
isInOldTownArea
Indicates that an entity is located within the designated old town area of a place.
-
B.
hasColonialUrbanLayout
Indicates that an urban area’s spatial organization and street pattern follow a design imposed during a colonial period, reflecting colonial planning principles and control.
-
C.
hasUrbanLayoutType
chosen
Indicates that an entity possesses or is characterized by a specific type or pattern of urban spatial layout.
-
D.
isInOldTownNetwork
Indicates that an entity is part of, or connected to, a designated "Old Town" network or system.
-
E.
hasStreetLayoutCenteredOn
Indicates that the spatial organization or pattern of streets in one place is arranged with a particular feature or location as its central focus or reference point.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e848b008190bd7314c9a0f884a3 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:01 p.m.