Triple

T27225492
Position Surface form Disambiguated ID Type / Status
Subject Höri E681398 entity
Predicate hasNeighboringCantonBorder P98239 FINISHED
Object canton of Aargau (nearby region) 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: canton of Aargau (nearby region) | Statement: [Höri, hasNeighboringCantonBorder, canton of Aargau (nearby region)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNeighboringCantonBorder
Context triple: [Höri, hasNeighboringCantonBorder, canton of Aargau (nearby region)]
  • A. hasNeighbouringCanton chosen
    Indicates that one canton is geographically adjacent to and shares a common border with another canton.
  • B. isInBorderCanton
    Indicates that an entity is located within a canton that shares a border with another country or region.
  • C. hasNeighboringCantonAcrossLake
    Indicates that one canton is directly across a lake from another canton, with the lake forming their mutual boundary.
  • D. neighboringCantonsRepresentedBy
    Indicates that the neighboring cantons of a given canton are represented by the specified entity or representative.
  • E. neighboringMunicipalityCanton
    Indicates that one municipality is geographically adjacent to another municipality within the same canton or across canton borders.
  • 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_69eefac9f64c8190a07490fe0c8b72a3 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69fbc9d1dba881908c399b8e1dc13ce2 completed May 6, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69fbc8ec03ac8190a757563f96fab283 completed May 6, 2026, 11:04 p.m.
Created at: April 27, 2026, 9:44 a.m.