Triple

T30577319
Position Surface form Disambiguated ID Type / Status
Subject Hügelland E778284 entity
Predicate hasTypicalAccessibility P196286 FINISHED
Object good for agriculture and settlement 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: good for agriculture and settlement | Statement: [Hügelland, hasTypicalAccessibility, good for agriculture and settlement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypicalAccessibility
Context triple: [Hügelland, hasTypicalAccessibility, good for agriculture and settlement]
  • A. hasTypicalAccess
    Indicates that one entity normally or customarily has the ability, permission, or means to access or use another entity.
  • B. hasAccessibleAccess
    Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
  • C. hasAccessibilityVariation
    Indicates that one entity differs from another in terms of accessibility features, conditions, or support.
  • D. hasAccessibilityLimitation
    Indicates that an entity is subject to specific constraints or limitations affecting its accessibility or ease of access.
  • E. valueAccessibility
    Indicates how easily or readily a value can be obtained, used, or understood by relevant parties.
  • 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_69f2249f8c148190ae7eb3912cde112a completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe1fd637c08190aa95cd2478c278cb completed May 8, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69fe19344bb481909b5e2144155e4add completed May 8, 2026, 5:11 p.m.
PDg Predicate description generation batch_69fe1fd58ad8819093d3d705e8521014 completed May 8, 2026, 5:39 p.m.
Created at: April 29, 2026, 8:23 p.m.