Triple

T18258824
Position Surface form Disambiguated ID Type / Status
Subject Dundee and Arbroath Railway E437290 entity
Predicate lineStillInUseAs P27206 FINISHED
Object part of Dundee–Aberdeen railway line 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: part of Dundee–Aberdeen railway line | Statement: [Dundee and Arbroath Railway, lineStillInUseAs, part of Dundee–Aberdeen railway line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lineStillInUseAs
Context triple: [Dundee and Arbroath Railway, lineStillInUseAs, part of Dundee–Aberdeen railway line]
  • A. isInUse
    Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
  • B. lineUses
    Indicates that a particular line (such as a route, service, or connection) makes use of or is implemented using a specified resource, infrastructure, or element.
  • C. stillUsedBy chosen
    Indicates that something continues to be used or relied upon by another entity at the present time.
  • D. lineUse
    Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
  • E. lineStatus
    Indicates the current operational or functional state of a line or connection within a system.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4fd8879e88190893f8da7c3529496 completed April 19, 2026, 4:06 p.m.
PD Predicate disambiguation batch_69e44fcdee748190bae6fb76e0cb22f3 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:34 a.m.