Triple

T7860941
Position Surface form Disambiguated ID Type / Status
Subject Shoreditch railway station E182494 entity
Predicate useAfterClosure P59269 FINISHED
Object goods traffic (via nearby facilities) 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: goods traffic (via nearby facilities) | Statement: [Shoreditch railway station, useAfterClosure, goods traffic (via nearby facilities)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: useAfterClosure
Context triple: [Shoreditch railway station, useAfterClosure, goods traffic (via nearby facilities)]
  • A. conditionAfterClosure chosen
    Indicates the state or circumstances that exist after a process, event, or entity has been formally closed or concluded.
  • B. classAfter
    Indicates that one class or course occurs later in time or sequence than another class or course.
  • C. controlledAfter
    Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
  • D. subjectToClosure
    Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
  • E. appliesToAfter
    Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
  • 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_69ca82887fd48190975896bf38c4596b completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb36bcb5cc8190a8a384ce0f020b9f completed March 31, 2026, 2:51 a.m.
PD Predicate disambiguation batch_69cae925ca388190ae4a01fa76e957e8 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:53 p.m.