Triple

T12565816
Position Surface form Disambiguated ID Type / Status
Subject Euston Square E295474 entity
Predicate stationCode P1289 FINISHED
Object EUS E51945 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: EUS | Statement: [Euston Square, stationCode, EUS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EUS
Context triple: [Euston Square, stationCode, EUS]
  • A. EUS chosen
    EUS is the three-letter National Rail station code for London Euston, a major central London railway terminus.
  • B. EUS
    EUS is the student-run engineering society at McGill University that represents and serves undergraduate engineering students through academic support, events, and services.
  • C. GUT
    GUT is a leading technical university in Gdańsk, Poland, known for its engineering, technology, and research programs.
  • D. EUN
    EUN was the Olympic country code for the Unified Team of former Soviet republics that competed together at the 1992 Winter and Summer Olympics.
  • E. EPU
    EPU is the three-letter station code used by Transport for London to identify East Putney tube station on the London Underground network.
  • 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_69d6ad9cac2c81908e8a7bed82d1e21d completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9549611c081909e611756f3cce7f0 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6558f87b081909ba179b49bae3913 completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 11:49 p.m.