Triple

T31574210
Position Surface form Disambiguated ID Type / Status
Subject Rattenberg E805647 entity
Predicate hasTraditionalBavarianCharacter P123967 FINISHED
Object true 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: true | Statement: [Rattenberg, hasTraditionalBavarianCharacter, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalBavarianCharacter
Context triple: [Rattenberg, hasTraditionalBavarianCharacter, true]
  • A. hasTraditionalCharm
    Indicates that something possesses a classic, old-fashioned, or culturally rooted appeal that evokes nostalgia or heritage.
  • B. hasTraditionalDialect
    Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
  • C. hasTraditionalRegionCharacter chosen
    Indicates that an entity possesses a characteristic or feature that is typical of, or traditionally associated with, a specific region.
  • D. hasTraditionalName
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • E. hasTraditionalCharacter
    Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
  • 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_69f348d3a86c8190a3e5e539a4dd125f completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fed357b2b4819084c709056a54461f completed May 9, 2026, 6:25 a.m.
PD Predicate disambiguation batch_69fed103d9cc81909b11619745110c61 completed May 9, 2026, 6:15 a.m.
Created at: April 30, 2026, 10:21 p.m.