Triple

T8774710
Position Surface form Disambiguated ID Type / Status
Subject Bergmannkiez (border area) E208547 entity
Predicate urbanHeritage P80580 FINISHED
Object historic building stock 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: historic building stock | Statement: [Bergmannkiez (border area), urbanHeritage, historic building stock]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: urbanHeritage
Context triple: [Bergmannkiez (border area), urbanHeritage, historic building stock]
  • A. designHeritage
    Indicates that one entity has influenced, shaped, or contributed to the design tradition or stylistic lineage of another entity.
  • B. heritageLocation
    Indicates that a location is recognized or designated as having cultural, historical, or natural heritage significance in relation to something.
  • C. heritageManagement
    Indicates the management, preservation, and regulation of cultural or natural heritage resources by responsible entities.
  • D. urbanHistoryFeature chosen
    Indicates a feature that plays a significant role in the historical development, events, or evolution of an urban area.
  • E. heritageValue
    Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
  • 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_69ca835edb4481909b4aafb616dc5eb7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f2ef3288190988bd69e8a02e741 completed March 31, 2026, 11:56 p.m.
PD Predicate disambiguation batch_69cc5c1aff3881908be6a9cbc9f50461 completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:41 p.m.