Triple

T16407924
Position Surface form Disambiguated ID Type / Status
Subject Bad Nauheim E398483 entity
Predicate vehicleRegistrationCode P1173 FINISHED
Object FB E1119895 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: FB | Statement: [Bad Nauheim, vehicleRegistrationCode, FB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FB
Context triple: [Bad Nauheim, vehicleRegistrationCode, FB]
  • A. FB
    FB is the common abbreviation for Fenerbahçe SK, one of Turkey’s most prominent multi-sport clubs best known for its successful football team based in Istanbul.
  • B. FB chosen
    FB is the vehicle registration code used on license plates for the district of Friedberg in the German state of Hesse.
  • C. FB
    FB is the internal chassis code used by Mazda to designate the first-generation RX-7 sports car.
  • D. Facebook
    Facebook is a major global social networking platform that allows users to connect, share content, and communicate online.
  • E. Facebook MPK21
    Facebook MPK21 is a large, Frank Gehry–designed office building on Meta’s Menlo Park campus that serves as one of the company’s primary headquarters spaces.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32870e44c8190aae7bc6e6022ceb7 completed April 18, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_6a003c64a05c8190a59e800ce2318052 completed May 10, 2026, 8:05 a.m.
Created at: April 10, 2026, 5:09 a.m.