Triple

T21855733
Position Surface form Disambiguated ID Type / Status
Subject Ludwigsfelde E539619 entity
Predicate vehicleRegistrationCode P1173 FINISHED
Object TF 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: TF | Statement: [Ludwigsfelde, vehicleRegistrationCode, TF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TF
Context triple: [Ludwigsfelde, vehicleRegistrationCode, TF]
  • A. TF
    TF is the French abbreviation for the Federal Supreme Court of Switzerland, the country’s highest judicial authority.
  • B. TF
    TF is the abbreviation for the Faculty of Engineering at the University of Freiburg, a German institution focused on engineering and technology education and research.
  • C. TF
    TF is the IATA airline designator assigned to Braathens Regional Airlines, a Swedish regional carrier.
  • D. TF
    TF is the ISO 3166-1 alpha-2 country code for the French Southern Territories, a French overseas territory in the southern Indian Ocean and Antarctica.
  • E. TF chosen
    TF is the vehicle registration code used for motor vehicles registered in the Spanish province of Santa Cruz de Tenerife in the Canary Islands.
  • 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_69e0c47829648190bbe2d1d7033768ec completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0d635b59c81908810480f3802b847 completed April 28, 2026, 3:45 p.m.
Created at: April 16, 2026, 6:56 p.m.