Triple

T3824950
Position Surface form Disambiguated ID Type / Status
Subject Verkehrsverbund Großraum Nürnberg E88663 entity
Predicate abbreviation P43 FINISHED
Object VGN E90420 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: VGN | Statement: [Verkehrsverbund Großraum Nürnberg, abbreviation, VGN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VGN
Context triple: [Verkehrsverbund Großraum Nürnberg, abbreviation, VGN]
  • A. VGN chosen
    VGN (Verkehrsverbund Großraum Nürnberg) is the public transport association that coordinates and manages integrated ticketing and services across the greater Nuremberg metropolitan area in Germany.
  • B. B-VG
    B-VG is the commonly used abbreviation for Austria’s Federal Constitutional Law, which forms the core of the country’s constitutional framework.
  • C. VBG
    VBG is the abbreviated name of the German association of botanical gardens, Verband Botanischer Gärten e.V.
  • D. VG
    VG is the two-letter ISO 3166 country code assigned to the British Virgin Islands.
  • E. VOG
    VOG is the IATA airport code for Volgograd International Airport, a regional air transport hub serving the city of Volgograd in Russia.
  • 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_69aed9538cf881909d9ce8ca4ac7c18c completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeeb6364fc8190bf8401743f1695d5 completed March 9, 2026, 3:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4fb4f41c88190b3040236462c37cc completed March 14, 2026, 6:08 a.m.
Created at: March 9, 2026, 3:17 p.m.