Triple

T13325576
Position Surface form Disambiguated ID Type / Status
Subject Imperial Wharf railway station E317432 entity
Predicate hasStationCode P1289 FINISHED
Object IMW E1034406 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: IMW | Statement: [Imperial Wharf railway station, hasStationCode, IMW]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IMW
Context triple: [Imperial Wharf railway station, hasStationCode, IMW]
  • A. IMW chosen
    IMW is the National Rail station code for Imperial Wharf railway station in London, United Kingdom.
  • B. IMB
    IMB is a Christian missionary organization of the Southern Baptist Convention that focuses on sending and supporting missionaries around the world.
  • C. IMB
    IMB was a large underground water Cherenkov detector in the United States, originally built to search for proton decay and later known for detecting neutrinos from supernova SN 1987A.
  • D. IM
    IM is the two-letter ISO 3166-1 alpha-2 country code assigned to the Isle of Man.
  • E. IIMN
    IIMN is a premier Indian business school located in Nagpur, offering postgraduate and doctoral programs in management.
  • 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_69d806b4d62c81908d4ced1665414be5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9992c1fec8190bcb6a6bb3c973a24 completed April 11, 2026, 12:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7266cfb3c8190ac9ccb7696d02922 completed May 3, 2026, 10:41 a.m.
Created at: April 9, 2026, 9:30 p.m.