Triple

T28351524
Position Surface form Disambiguated ID Type / Status
Subject Naumburg tramway E718110 entity
Predicate heritagePurpose P178287 FINISHED
Object preservation of historic urban tramway 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: preservation of historic urban tramway | Statement: [Naumburg tramway, heritagePurpose, preservation of historic urban tramway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heritagePurpose
Context triple: [Naumburg tramway, heritagePurpose, preservation of historic urban tramway]
  • A. heritageFor
    Indicates that something serves as a source, basis, or contributing legacy for another entity’s heritage or tradition.
  • B. heritageValue
    Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
  • C. heritageType
    Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
  • D. heritageService
    Indicates that an entity provides, manages, or is associated with services related to the preservation, interpretation, or promotion of cultural or natural heritage.
  • E. heritageManagement
    Indicates the management, preservation, and regulation of cultural or natural heritage resources by responsible entities.
  • 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_69eff6ec27b481908c8d7b86c47893d9 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f70e8755a48190931eaa77946f9460 completed May 3, 2026, 8:59 a.m.
PD Predicate disambiguation batch_69f70abc00848190a1c3f495ef6c8dc6 completed May 3, 2026, 8:43 a.m.
PDg Predicate description generation batch_69f70e854b9c8190a3416e2189e17742 completed May 3, 2026, 8:59 a.m.
Created at: April 28, 2026, 12:46 a.m.