Triple

T36614177
Position Surface form Disambiguated ID Type / Status
Subject Sulzfeld am Main E903556 entity
Predicate hasTownFortifications P22477 FINISHED
Object historic village walls 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 village walls | Statement: [Sulzfeld am Main, hasTownFortifications, historic village walls]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTownFortifications
Context triple: [Sulzfeld am Main, hasTownFortifications, historic village walls]
  • A. hasFortifications chosen
    Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
  • B. hasFortificationsFrom
    Indicates that an entity possesses or is protected by fortifications that originate from or were constructed by another specified source or period.
  • C. wasFortifiedBy
    Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
  • D. fortificationTypeDefended
    Indicates the specific type of fortification that an entity is responsible for defending or protecting.
  • E. isFortifiedCity
    Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
  • 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_69f76e6960e4819092047756ceb9a17e completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fd68abf52881909c5a390c362b7c59 completed May 8, 2026, 4:38 a.m.
PD Predicate disambiguation batch_69fd6812d0c88190930d8fa2d4b92490 completed May 8, 2026, 4:35 a.m.
Created at: May 3, 2026, 4:11 p.m.