Triple

T8554082
Position Surface form Disambiguated ID Type / Status
Subject NS Sprinter E202518 entity
Predicate stopPolicy P83592 FINISHED
Object stops at all or most intermediate stations 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: stops at all or most intermediate stations | Statement: [NS Sprinter, stopPolicy, stops at all or most intermediate stations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stopPolicy
Context triple: [NS Sprinter, stopPolicy, stops at all or most intermediate stations]
  • A. stopsPattern
    Indicates that one entity halts, interrupts, or prevents the continuation of a recurring or structured pattern involving another entity.
  • B. terminationPolicyEnded
    Indicates that a previously established termination policy has come to an end and is no longer in effect.
  • C. terminationPolicyApplied
    Indicates that a specific termination policy has been enforced or put into effect for the related entity or relationship.
  • D. shutdownPeriod
    Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
  • E. expirationPolicy
    Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
  • 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_69ca832610e08190b3b6c6cd2c250255 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe8894e7c8190bc0ae2ceec473ecb completed March 31, 2026, 3:30 p.m.
PD Predicate disambiguation batch_69cbd1160fcc8190aa380a73610af731 completed March 31, 2026, 1:50 p.m.
PDg Predicate description generation batch_69cbe30e37ac8190b685df36274602b5 completed March 31, 2026, 3:06 p.m.
Created at: March 30, 2026, 6:19 p.m.