Triple

T27516530
Position Surface form Disambiguated ID Type / Status
Subject North Union Railway E694579 entity
Predicate openedMainLineBetween P152624 FINISHED
Object Wigan NE NERFINISHED

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: Wigan | Statement: [North Union Railway, openedMainLineBetween, Wigan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openedMainLineBetween
Context triple: [North Union Railway, openedMainLineBetween, Wigan]
  • A. openedRouteBetween chosen
    Indicates that an agent initiated or established a route or connection enabling movement or communication between two locations or entities.
  • B. openedFirstLine
    Indicates that one entity initiated the opening of something (e.g., a file, document, or interface) before any other entity did, being the first to perform the opening action.
  • C. openingLineStatus
    Indicates the status or condition of an entity’s opening line, such as whether it exists, is valid, or meets a specified criterion.
  • D. openedBetween
    Indicates that an entity was opened during a time interval that falls between two specified temporal bounds.
  • E. openingLine
    Indicates that one entity is the first line or initial statement that begins another entity, such as a text, speech, or conversation.
  • 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_69ef53842afc8190ba6bd4e4999bda67 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f6cee45590819086e489bfccbe4ac3 completed May 3, 2026, 4:28 a.m.
PD Predicate disambiguation batch_69f6cc1188708190b8f0f56e595e6057 completed May 3, 2026, 4:16 a.m.
Created at: April 27, 2026, 1:18 p.m.