Triple

T14385965
Position Surface form Disambiguated ID Type / Status
Subject BW E356722 entity
Predicate refersTo P37 FINISHED
Object Borsigwerke E72033 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: Borsigwerke | Statement: [BW, refersTo, Borsigwerke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borsigwerke
Context triple: [BW, refersTo, Borsigwerke]
  • A. Borsigwerke chosen
    Borsigwerke is a Berlin U-Bahn station on line U6 serving the Tegel district in the city’s northwest.
  • B. Maschinenbau-Anstalt Borsig
    Maschinenbau-Anstalt Borsig was a prominent 19th-century German engineering and locomotive manufacturing company that became one of Europe’s leading producers of steam locomotives.
  • C. Deutsche Werke AG
    Deutsche Werke AG was a German state-owned industrial and shipbuilding company, notably active in naval construction during the early to mid-20th century.
  • D. Borsig
    Borsig is a German surname most prominently associated with August Borsig, a 19th-century industrialist and locomotive manufacturer.
  • E. Gothaer Waggonfabrik
    Gothaer Waggonfabrik was a German industrial company best known for producing military aircraft, including heavy bombers, during World War I.
  • 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_69d827927c988190ad98bb0360981783 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9025cff881908c08224d90d9f750 completed April 14, 2026, 7:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5513e8888190bc6b6cb33fd9b670 completed May 8, 2026, 3:14 a.m.
Created at: April 10, 2026, 1:16 a.m.