Triple

T12489411
Position Surface form Disambiguated ID Type / Status
Subject 1995 Stock E298521 entity
Predicate compatibleWith P203 FINISHED
Object Northern line signalling system E61912 NE 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: Northern line signalling system | Statement: [1995 Stock, compatibleWith, Northern line signalling system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Northern line signalling system
Context triple: [1995 Stock, compatibleWith, Northern line signalling system]
  • A. Northern line chosen
    The Northern line is a major London Underground route running north–south across the city, serving key central and suburban areas.
  • B. S1 Line
    The S1 Line is a medium-capacity maglev rapid transit line in the Beijing Subway system serving the western suburbs of the city.
  • C. S1 Line
    The S1 Line is a rapid transit route within the Nanjing Metro system in Nanjing, China, providing urban rail service along one of the city’s key corridors.
  • D. Northern Line
    The Northern Line is a major commuter rail route in the Merseyrail network serving Liverpool and surrounding areas in North West England.
  • E. S1 line
    The S1 line is a route of the Rhine-Main S-Bahn network serving the Frankfurt metropolitan area and surrounding region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6ada377208190a36011199a4d8558 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94de1db9481909ddf70eb81cdb714 completed April 10, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64ba9e1108190b74984d9da9baebe completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:56 p.m.