Triple

T7434503
Position Surface form Disambiguated ID Type / Status
Subject Fauldhouse railway station E171575 entity
Predicate lineUse P76380 FINISHED
Object commuter services 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: commuter services | Statement: [Fauldhouse railway station, lineUse, commuter services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lineUse
Context triple: [Fauldhouse railway station, lineUse, commuter services]
  • A. 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.
  • B. lineStandard
    Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
  • C. usesLineCharacteristic
    Indicates that one entity employs or is based on a specific characteristic or property of a line.
  • D. lineType
    Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
  • E. usesLineCode
    Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
  • 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_69c68a64228c8190affaec2a8127ce7b completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f327480481909c4691fd3333e2ae completed March 27, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69c6f038582c8190bac77c9b5a34b862 completed March 27, 2026, 9:01 p.m.
PDg Predicate description generation batch_69c6f0be2b1c8190bea06100a7caef2b completed March 27, 2026, 9:03 p.m.
Created at: March 27, 2026, 3:13 p.m.