Triple

T1602138
Position Surface form Disambiguated ID Type / Status
Subject Manchester Victoria railway station E34416 entity
Predicate stationCode P1289 FINISHED
Object MCV E5752 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: MCV | Statement: [Manchester Victoria railway station, stationCode, MCV]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MCV
Context triple: [Manchester Victoria railway station, stationCode, MCV]
  • A. MCV chosen
    MCV is the National Rail station code for Manchester Victoria railway station, a major rail hub in Manchester, England.
  • B. MCA
    MCA was a major American record label and entertainment company known for signing prominent artists and producing a wide range of popular music releases.
  • C. MCA
    MCA is the UK government executive agency responsible for maritime safety, search and rescue coordination, and preventing pollution from ships in UK waters.
  • D. Mc
    Mc is a Gaelic patronymic prefix meaning "son of," commonly found in Scottish and Irish surnames.
  • E. MCRC
    MCRC is the United States Marine Corps Recruiting Command responsible for enlisting and accessing new Marines into the Corps.
  • 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_69a885fea6a481909fe83ba6441f1774 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9094b7b3c8190a5b08699e07a770f completed March 5, 2026, 4:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad46ad15b081908b59df18224c7a8f completed March 8, 2026, 9:51 a.m.
Created at: March 4, 2026, 7:28 p.m.