Triple

T19873168
Position Surface form Disambiguated ID Type / Status
Subject Karlberg Canal E477571 entity
Predicate cityDistrictBoundary P108932 FINISHED
Object boundary between Stockholm and Solna 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: boundary between Stockholm and Solna | Statement: [Karlberg Canal, cityDistrictBoundary, boundary between Stockholm and Solna]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityDistrictBoundary
Context triple: [Karlberg Canal, cityDistrictBoundary, boundary between Stockholm and Solna]
  • A. schoolDistrictBoundary
    Indicates the geographic boundary within which a particular school district has jurisdiction and provides educational services.
  • B. borderingLocalGovernmentArea
    Indicates that one local government area shares a common boundary with another local government area.
  • C. fareBoundaryBetween
    Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
  • D. geographicBoundary chosen
    Indicates that one entity serves as a limiting border or edge that defines the geographic extent or separation of another entity.
  • E. borderingCensusDivision
    Indicates that one census division shares a common boundary with another census division.
  • 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_69d8e51e7d948190aedbcd6c30361c39 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e658d92f9c8190b363587ed1881c2c completed April 20, 2026, 4:48 p.m.
PD Predicate disambiguation batch_69e537e8c4e481909fe95d795b4864e7 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:51 p.m.