Triple

T10203086
Position Surface form Disambiguated ID Type / Status
Subject SL postcode area E238932 entity
Predicate postcodeAreaCode P920 FINISHED
Object SL E520648 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: SL | Statement: [SL postcode area, postcodeAreaCode, SL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SL
Context triple: [SL postcode area, postcodeAreaCode, SL]
  • A. SL
    The Mercedes-Benz SL is a long-running line of luxury grand touring roadsters renowned for combining high performance with elegant design and advanced technology.
  • B. SL
    SL is a German vehicle registration code used on license plates to identify cars registered in the Saalekreis district of Saxony-Anhalt.
  • C. SL
    SL is the common abbreviation used for the Salt Lake Bees, a Minor League Baseball team based in Salt Lake City, Utah.
  • D. SL
    SL is a mid-range trim level designation used by Holden for certain Torana models, offering additional comfort and convenience features over the base variants.
  • E. SL chosen
    SL is the two-letter ISO country code for Sierra Leone, a West African nation on the Atlantic coast.
  • 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_69ca84e1ea088190b38162e43d4cfa8f completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdee4239c08190b40f5cc19c3db3c7 completed April 2, 2026, 4:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d317fcdf18819092d0f3f216edffdc completed April 6, 2026, 2:18 a.m.
Created at: March 30, 2026, 9:14 p.m.