Triple

T31292390
Position Surface form Disambiguated ID Type / Status
Subject OS Landranger 135 E797973 entity
Predicate includesTopography P202989 FINISHED
Object contour lines 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: contour lines | Statement: [OS Landranger 135, includesTopography, contour lines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesTopography
Context triple: [OS Landranger 135, includesTopography, contour lines]
  • A. hasTopographicEffect
    Indicates that one entity causes or contributes to a change or influence on the physical terrain or topography of another entity or area.
  • B. topographyBasedOn
    Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
  • C. hasTopographicContext
    Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
  • D. associatedTopography
    Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
  • E. topographicSignificance
    Indicates the degree to which a geographic feature stands out or is prominent in the surrounding terrain based on its elevation and relief.
  • 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_69f224dfde288190af313f3c221c857e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a00d8ba18808190976682088a02a9a8 completed May 10, 2026, 7:12 p.m.
PD Predicate disambiguation batch_6a00d85fad64819084f424ec8ecd3b57 completed May 10, 2026, 7:11 p.m.
PDg Predicate description generation batch_6a00d8b8eac08190809c78998e09c47c completed May 10, 2026, 7:12 p.m.
Created at: April 29, 2026, 9:14 p.m.