Triple

T4106631
Position Surface form Disambiguated ID Type / Status
Subject Daimler AG E88466 entity
Predicate brand P1500 FINISHED
Object Maybach E318782 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: Maybach | Statement: [Daimler AG, brand, Maybach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maybach
Context triple: [Daimler AG, brand, Maybach]
  • A. Maybach chosen
    Maybach is a historic German luxury automobile and engine brand renowned for its high-end engineering and association with elite, chauffeur-driven cars.
  • B. Maybach HL 120 TRM
    The Maybach HL 120 TRM is a German World War II-era 12-cylinder gasoline tank engine widely used in medium armored vehicles such as the Panzer IV.
  • C. Maybach HL210 P45
    The Maybach HL210 P45 was a German World War II-era V12 gasoline tank engine used in early models of the Tiger I heavy tank.
  • D. Maybach HL230 P45
    The Maybach HL230 P45 was a powerful German V-12 gasoline tank engine used in heavy World War II armored vehicles such as the Tiger I and Panther.
  • E. Bentley Mulliner
    Bentley Mulliner is Bentley Motors’ bespoke coachbuilding and customization division, renowned for creating highly personalized, ultra-luxury versions of the brand’s cars.
  • 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_69aed9484fb881909146f4c772ad277c completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af019c7a3c8190a503ce80e87dc3b3 completed March 9, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b56b7f88948190b87242e706a488c0 completed March 14, 2026, 2:06 p.m.
Created at: March 9, 2026, 3:40 p.m.