Triple

T31071871
Position Surface form Disambiguated ID Type / Status
Subject Olsztyn–Skandawa railway line E791840 entity
Predicate hasEndpointLocality P26386 FINISHED
Object Skandawa NE NERFINISHED

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: Skandawa | Statement: [Olsztyn–Skandawa railway line, hasEndpointLocality, Skandawa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEndpointLocality
Context triple: [Olsztyn–Skandawa railway line, hasEndpointLocality, Skandawa]
  • A. containsLocality
    Indicates that one place or area geographically includes or encompasses another locality within its boundaries.
  • B. hasEndpointCity chosen
    Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
  • C. hasLocalConnections
    Indicates that an entity maintains relationships, ties, or affiliations within a specific local area or community.
  • D. hasBorderLocality
    Indicates that one locality is situated along or adjacent to the border of another locality.
  • E. hasPrimaryEndpoint
    Indicates that an entity designates another entity as its main or most important endpoint or target location.
  • 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_69f224ccdbbc81909b0cdb4cc2d70c7a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f7c29e1b848190b945c6c6120a5330 completed May 3, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f7c1b6e7a881908deb96bedb2713f4 completed May 3, 2026, 9:44 p.m.
Created at: April 29, 2026, 9:01 p.m.