Triple

T6592466
Position Surface form Disambiguated ID Type / Status
Subject British Rail Class 171 E148394 entity
Predicate multipleWorkingCompatibility P64407 FINISHED
Object Southern Electrostar units (via Dellner couplers) 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: Southern Electrostar units (via Dellner couplers) | Statement: [British Rail Class 171, multipleWorkingCompatibility, Southern Electrostar units (via Dellner couplers)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: multipleWorkingCompatibility
Context triple: [British Rail Class 171, multipleWorkingCompatibility, Southern Electrostar units (via Dellner couplers)]
  • A. multipleWorkingWith chosen
    Indicates that an entity is simultaneously collaborating or engaged in work with more than one other entity.
  • B. hasMultipleWorking
    Indicates that an entity is associated with more than one working instance, role, or configuration simultaneously.
  • C. multipleAccess
    Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
  • D. canOperateInMultiple
    Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
  • E. compatibleStand
    Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
  • 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_69c687e7b8688190811ffee72e096468 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6c07cdf048190945ca5810fb1de88 completed March 27, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69c6acfb462481909cb7aff5af4bca9d completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:55 p.m.