Triple
T27721394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Centres of Stralsund and Wismar |
E698963
|
entity |
| Predicate | hasSignificantBuildingType |
P50464
|
FINISHED |
| Object | town hall |
—
|
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: town hall | Statement: [Historic Centres of Stralsund and Wismar, hasSignificantBuildingType, town hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantBuildingType Context triple: [Historic Centres of Stralsund and Wismar, hasSignificantBuildingType, town hall]
-
A.
containsBuildingType
chosen
Indicates that a location or area includes at least one building of the specified type.
-
B.
significantBuildingWithin
Indicates that a building of notable importance is located inside the boundaries of another specified area or structure.
-
C.
hasMainBuildings
Indicates that one entity possesses or is associated with one or more primary or principal buildings.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 3:07 p.m.