Triple

T4847901
Position Surface form Disambiguated ID Type / Status
Subject Getreidegasse E108335 entity
Predicate hasSignageTradition P19423 FINISHED
Object guild signs indicating trades 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: guild signs indicating trades | Statement: [Getreidegasse, hasSignageTradition, guild signs indicating trades]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSignageTradition
Context triple: [Getreidegasse, hasSignageTradition, guild signs indicating trades]
  • A. hasSignage
    Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
  • B. hasSignageType
    Indicates the specific category or kind of signage associated with an object, location, or entity.
  • C. hasSignageName
    Indicates that an entity has a specific name or label as it appears on its physical signage.
  • D. hasCulturalSignificanceFor
    Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
  • E. hasTraditionIn chosen
    Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
  • 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_69bd4409b264819085ab855f3eb5381a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ddd17d881909f7731ff2b460e83 completed March 20, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69bd6c2557388190a2d15571bacd24f3 completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:25 p.m.