Triple

T6093471
Position Surface form Disambiguated ID Type / Status
Subject Southern E135821 entity
Predicate parentCompany P254 FINISHED
Object Govia E549600 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: Govia | Statement: [Southern, parentCompany, Govia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Govia
Context triple: [Southern, parentCompany, Govia]
  • A. Govia chosen
    Govia is a major British train operating company formed as a joint venture between the Go-Ahead Group and Keolis, running several rail franchises in the United Kingdom.
  • B. Abellio
    Abellio is a Dutch-based public transport company that operates train and bus services in the United Kingdom and parts of Europe.
  • C. Keolis
    Keolis is a major French public transport operator that manages and operates bus, tram, metro, and rail networks in numerous cities worldwide.
  • D. Systra
    Systra is a global engineering and consulting firm specializing in mass transit and rail infrastructure projects.
  • E. Arriva
    Arriva is a major European public transport company that operates bus, coach, train, tram, and waterbus services across multiple countries.
  • 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_69c0087cd3c48190b459848c72d84eb1 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c057ac8c7481909fb22cf157be45ce completed March 22, 2026, 8:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69c125365a7481909e40d01c2d3590aa completed March 23, 2026, 11:34 a.m.
Created at: March 22, 2026, 4:12 p.m.