Triple

T8031385
Position Surface form Disambiguated ID Type / Status
Subject Manchester, Sheffield and Lincolnshire Railway interests (partial) E186986 entity
Predicate acquisitionScope P80673 FINISHED
Object selected lines 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: selected lines | Statement: [Manchester, Sheffield and Lincolnshire Railway interests (partial), acquisitionScope, selected lines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: acquisitionScope
Context triple: [Manchester, Sheffield and Lincolnshire Railway interests (partial), acquisitionScope, selected lines]
  • A. accessScope
    Indicates the extent or boundaries of access that one entity has to another entity or resource.
  • B. availabilityScope
    Indicates the extent or context within which something is available, accessible, or applicable.
  • C. acquiredFor
    Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
  • D. operationalScope
    Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
  • E. acquisitionTarget
    Indicates that one entity is the intended or actual company or asset being acquired by another in a merger or acquisition transaction.
  • 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_69ca82ae2d1081909dbfee42b41db419 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3eef921081908d0ea21f142c175a completed March 31, 2026, 3:26 a.m.
PD Predicate disambiguation batch_69cb049688208190b32088bd2c5930bc completed March 30, 2026, 11:17 p.m.
PDg Predicate description generation batch_69cb14bcbbc0819094a98e7ffffb7a40 completed March 31, 2026, 12:26 a.m.
Created at: March 30, 2026, 5:22 p.m.