Triple

T38032845
Position Surface form Disambiguated ID Type / Status
Subject Krzyż Wielkopolski E948960 entity
Predicate railwayLinePassesThrough P160930 FINISHED
Object Poznań–Szczecin railway 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: Poznań–Szczecin railway | Statement: [Krzyż Wielkopolski, railwayLinePassesThrough, Poznań–Szczecin railway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayLinePassesThrough
Context triple: [Krzyż Wielkopolski, railwayLinePassesThrough, Poznań–Szczecin railway]
  • A. railwayLine
    Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
  • B. railwayLineLocation chosen
    Indicates that a railway line is located in, passes through, or is associated with a specific geographic area or place.
  • C. railwayRunsAlong
    Indicates that a railway line extends parallel to and in close proximity with another feature or route for a significant distance.
  • D. isRailwayIn
    Indicates that a railway is located within or passes through a specified geographic or administrative area.
  • E. railwayLineNow
    Indicates that a previously existing railway line has been replaced, succeeded, or is currently represented by a new or different railway line.
  • 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_69f76efd1bc48190a729097fe5177b61 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcf1b3d9a08190850b388308656266 completed May 7, 2026, 8:10 p.m.
PD Predicate disambiguation batch_69fcf0226d8c8190b23dceafb1794995 completed May 7, 2026, 8:03 p.m.
Created at: May 3, 2026, 4:20 p.m.