Triple

T26865125
Position Surface form Disambiguated ID Type / Status
Subject Ranst E676443 entity
Predicate hasProtectedHeritage P163831 FINISHED
Object historic farms 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 farms | Statement: [Ranst, hasProtectedHeritage, historic farms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProtectedHeritage
Context triple: [Ranst, hasProtectedHeritage, historic farms]
  • A. hasHeritageValueFor
    Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
  • B. hasCulturalProtection
    Indicates that an entity is subject to legal or formal measures intended to preserve and safeguard its cultural value or heritage.
  • C. hasHeritageOfSite
    Indicates that a site possesses or is associated with a particular heritage designation, tradition, or cultural-historical value.
  • D. isPartOfHeritage
    Indicates that something belongs to, contributes to, or is recognized as a component of a broader cultural, historical, or natural heritage.
  • E. hasHeritageElements chosen
    Indicates that something contains or includes elements that are part of a cultural, historical, or natural 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_69eee9ba94bc8190b44c5d4397d04ecd completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69fd592e48cc81909d754cc6c4bd99ae completed May 8, 2026, 3:31 a.m.
PD Predicate disambiguation batch_69fd58b7f9b881909dc099b28d567784 completed May 8, 2026, 3:30 a.m.
Created at: April 27, 2026, 5:28 a.m.