Triple

T18804725
Position Surface form Disambiguated ID Type / Status
Subject BMVI E459841 entity
Predicate usedAbbreviation P43 FINISHED
Object BMVI NE NERFINISHED

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: BMVI | Statement: [BMVI, usedAbbreviation, BMVI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BMVI
Context triple: [BMVI, usedAbbreviation, BMVI]
  • A. BMVI chosen
    BMVI is the abbreviation for Germany’s former Federal Ministry responsible for transport policy and digital infrastructure development.
  • B. BMVI
    BMVI is an EU funding instrument focused on strengthening border management and visa policy implementation across member states.
  • C. BMV
    BMV is the National Rail station code for Bromsgrove railway station in Worcestershire, England.
  • D. BMV
    BMV is the common abbreviation for the Indiana Bureau of Motor Vehicles, the state agency responsible for driver licensing, vehicle registration, and related motor vehicle services in Indiana.
  • E. BMV
    BMV is the main stock exchange in Mexico, serving as the country’s central marketplace for trading equities and other financial instruments.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d398c7d4819091cb2f7e48948aeb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5a025faf48190be07086071df5b34 completed April 20, 2026, 3:40 a.m.
Created at: April 10, 2026, 11:53 a.m.