Triple

T6493828
Position Surface form Disambiguated ID Type / Status
Subject British Rail Class 168 E148104 entity
Predicate successorFamily P71053 FINISHED
Object basis for later Turbostar variants 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: basis for later Turbostar variants | Statement: [British Rail Class 168, successorFamily, basis for later Turbostar variants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorFamily
Context triple: [British Rail Class 168, successorFamily, basis for later Turbostar variants]
  • A. successor
    Indicates that one entity directly follows another in an ordered sequence or position.
  • B. successorType
    Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
  • C. successorInHouse
    Indicates that one entity directly follows another in holding a position or role within the same house or lineage.
  • D. ethnicSuccessor
    Indicates that one ethnic group is the successor or continuation of another, typically inheriting its identity, culture, or population in a historical or social sense.
  • E. successorSystem
    Indicates that one system directly follows and replaces another in function, role, or version.
  • 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_69c009088f3081909cd467b05919de30 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06ab6abbc8190a4971ad5a654b0cd completed March 22, 2026, 10:18 p.m.
PD Predicate disambiguation batch_69c06740bebc81909d9d6956baa2bcb9 completed March 22, 2026, 10:03 p.m.
PDg Predicate description generation batch_69c067f1ef148190bc0355abe83f7e16 completed March 22, 2026, 10:06 p.m.
Created at: March 22, 2026, 4:53 p.m.