Triple

T24932780
Position Surface form Disambiguated ID Type / Status
Subject Craigieburn railway station E623232 entity
Predicate isElectrifiedTerminus P65516 FINISHED
Object yes 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: yes | Statement: [Craigieburn railway station, isElectrifiedTerminus, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isElectrifiedTerminus
Context triple: [Craigieburn railway station, isElectrifiedTerminus, yes]
  • A. isElectricRailway
    Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
  • B. isElectrifiedSince
    Indicates that an entity has had electrical power or electrification continuously from a specified point in time onward.
  • C. isElectrifiedSectionOf
    Indicates that one section or segment is a part of a larger entity and has been equipped with electrical power or electrification.
  • D. electrificationTerminusOf chosen
    Indicates that a location or point serves as the end of an electrified section of a route, line, or network.
  • E. railElectrificationIncludes
    Indicates that a rail electrification system or project encompasses, covers, or incorporates a specified segment, component, or area of railway infrastructure.
  • 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_69e2fac6b5a48190a1c38857f00915a9 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f453035f508190be83a3d521723acf completed May 1, 2026, 7:15 a.m.
PD Predicate disambiguation batch_69f44d77f6e88190a4643ab2cbef567b completed May 1, 2026, 6:51 a.m.
Created at: April 18, 2026, 5:30 a.m.