Triple

T8668411
Position Surface form Disambiguated ID Type / Status
Subject FuG 220 Lichtenstein SN-2 radar E205732 entity
Predicate manufacturer P490 FINISHED
Object Telefunken E91046 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: Telefunken | Statement: [FuG 220 Lichtenstein SN-2 radar, manufacturer, Telefunken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Telefunken
Context triple: [FuG 220 Lichtenstein SN-2 radar, manufacturer, Telefunken]
  • A. Telefunken chosen
    Telefunken is a historic German electronics and television brand known for its radios, audio equipment, and consumer electronics.
  • B. Fitel
    Fitel was a financial technology startup where Jeff Bezos worked early in his career, before joining D. E. Shaw and later founding Amazon.
  • C. Erlecom
    Erlecom is a small village in the Dutch province of Gelderland, situated along the Waal River within the municipality of Berg en Dal.
  • D. Telesystem-Mesko
    Telesystem-Mesko is a Polish defense company known for developing advanced guided missile and precision weapon systems.
  • E. Kenwood
    Kenwood is a small community in California’s Sonoma Valley known for its wineries, vineyards, and scenic rural charm.
  • 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_69ca83516ae88190aefe034b3bc589e3 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc48a48b548190b78259072b1224ee completed March 31, 2026, 10:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69cecd1ca88c8190a3b2ca79a7204248 completed April 2, 2026, 8:10 p.m.
Created at: March 30, 2026, 6:31 p.m.