Triple

T13667008
Position Surface form Disambiguated ID Type / Status
Subject South Ealing station E327146 entity
Predicate lineTransferredToPiccadilly P42669 FINISHED
Object 1935-03-04 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: 1935-03-04 | Statement: [South Ealing station, lineTransferredToPiccadilly, 1935-03-04]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lineTransferredToPiccadilly
Context triple: [South Ealing station, lineTransferredToPiccadilly, 1935-03-04]
  • A. isOnPiccadillyLineBranch
    Indicates that something (typically a station or track segment) lies on a branch of the Piccadilly Line rather than on its main central section.
  • B. transferredToLondonUnderground chosen
    Indicates that something or someone has been moved from a previous context or system into the London Underground network or organization.
  • C. hasPiccadillyPlatformsBetween
    Indicates that one station has Piccadilly line platforms located between it and another station along the route.
  • D. isAdjacentStationOnPiccadillyLine
    Indicates that two stations are directly next to each other as consecutive stops on the Piccadilly Line.
  • E. hasPiccadillyLinePlatforms
    Indicates that an entity has platforms served by the Piccadilly Line.
  • 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc623fcc88190bbad97541c040b7a completed April 12, 2026, 4:19 p.m.
PD Predicate disambiguation batch_69dbbe8d8d0881908d6e89954f44eed4 completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 9:52 p.m.