Triple

T17026520
Position Surface form Disambiguated ID Type / Status
Subject USAV E413077 entity
Predicate usesAbbreviation P43 FINISHED
Object BLV E507205 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: BLV | Statement: [USAV, usesAbbreviation, BLV]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BLV
Context triple: [USAV, usesAbbreviation, BLV]
  • A. BLV
    BLV is the Swiss Federal Food Safety and Veterinary Office, the national authority responsible for protecting public health and animal welfare through regulation and oversight of food safety and veterinary matters.
  • B. BLV chosen
    BLV is the IATA airport code for MidAmerica St. Louis Airport, a joint-use civilian and military airfield at Scott Air Force Base in Illinois, USA.
  • C. BVL
    BVL is Germany’s Federal Office of Consumer Protection and Food Safety, the national authority responsible for ensuring food safety and protecting consumer health.
  • D. BVV
    BVV is a major trade fair and exhibition complex in Brno, Czech Republic, hosting large international fairs, conferences, and events.
  • E. BVV
    BVV is the common abbreviation for the district-level representative assemblies that serve as local parliaments in the boroughs of Berlin, Germany.
  • 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_69d886cc4170819093deddc7b8b4b6a7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d5d5ed388190871aa738cac04b65 completed April 18, 2026, 7:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012ed2ad708190a250762997611569 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:33 a.m.