Triple

T23649112
Position Surface form Disambiguated ID Type / Status
Subject Ashbourne Tunnel E584119 entity
Predicate hasTrackbedConversion P153032 FINISHED
Object railway to multi‑use trail conversion 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: railway to multi‑use trail conversion | Statement: [Ashbourne Tunnel, hasTrackbedConversion, railway to multi‑use trail conversion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrackbedConversion
Context triple: [Ashbourne Tunnel, hasTrackbedConversion, railway to multi‑use trail conversion]
  • A. hasRail
    Indicates that something is equipped with, includes, or is connected to a rail or rail system.
  • B. hasLocomotive
    Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
  • C. hasConveyorBeltTo
    Indicates that one location, machine, or area is connected to another by a conveyor belt that transports items between them.
  • D. hasRailwayTraction
    Indicates that a railway system, line, or vehicle uses a specified type or method of traction (e.g., electric, diesel, steam) for its propulsion.
  • E. hasRailMode
    Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
  • F. None of above. chosen

Provenance (4 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_69e248fefafc81909656921192f30e80 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b287606881909926de5efd882a76 completed April 29, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69f118d7903c8190bb590a71771e93af completed April 28, 2026, 8:30 p.m.
PDg Predicate description generation batch_69f1233300bc8190ac1639bdca1d7d99 completed April 28, 2026, 9:14 p.m.
Created at: April 17, 2026, 6:49 p.m.