Triple

T20396384
Position Surface form Disambiguated ID Type / Status
Subject Northern Latvia E500215 entity
Predicate hasReliefCharacteristic P22470 FINISHED
Object undulating terrain 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: undulating terrain | Statement: [Northern Latvia, hasReliefCharacteristic, undulating terrain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReliefCharacteristic
Context triple: [Northern Latvia, hasReliefCharacteristic, undulating terrain]
  • A. hasReliefFeature chosen
    Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
  • B. hasRelief
    Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
  • C. hasReliefRange
    Indicates a relationship where an entity is associated with a specified range or interval of relief (e.g., elevation difference or surface variation) values.
  • D. hasReliefOf
    Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
  • E. hasReliefsFrom
    Indicates that one entity experiences a reduction or alleviation of symptoms, problems, or burdens as a result of another entity.
  • 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_69e0b4a71ebc8190b153a36c738730f4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6798b6640819085d5b12dc35633fe completed April 20, 2026, 7:07 p.m.
PD Predicate disambiguation batch_69e5765d7cb48190adec18d6d1e3d263 completed April 20, 2026, 12:42 a.m.
Created at: April 16, 2026, 11:28 a.m.