Triple

T6336922
Position Surface form Disambiguated ID Type / Status
Subject DBY E142512 entity
Predicate threeLetterCode P418 FINISHED
Object DBY E142512 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: DBY | Statement: [DBY, threeLetterCode, DBY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DBY
Context triple: [DBY, threeLetterCode, DBY]
  • A. DBY chosen
    DBY is the National Rail station code for Derby railway station, a major rail hub in Derby, England.
  • B. DB1
    DB1 is the stock ticker symbol for Deutsche Börse AG, a major German exchange organization that operates the Frankfurt Stock Exchange and related financial market infrastructure.
  • C. DBX
    DBX is the stock ticker symbol for Dropbox, Inc., a cloud-based file storage and collaboration company traded on the NASDAQ.
  • D. BDB
    BDB is the IATA airport code for Bundaberg Airport, a regional airport serving the city of Bundaberg in Queensland, Australia.
  • E. YDB
    YDB is the common abbreviation for the Yokohama DeNA BayStars, a professional baseball team in Japan’s Nippon Professional Baseball league.
  • 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_69c008d4d8e88190ad301c05b08722ac completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0654c63508190b51f7b622388e5ad completed March 22, 2026, 9:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69c604307b388190bbc59f5f57cb4bbe completed March 27, 2026, 4:14 a.m.
Created at: March 22, 2026, 4:30 p.m.