Triple

T15103741
Position Surface form Disambiguated ID Type / Status
Subject Jack Heuer E360732 entity
Predicate brand P1500 FINISHED
Object Heuer E13778 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: Heuer | Statement: [Jack Heuer, brand, Heuer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heuer
Context triple: [Jack Heuer, brand, Heuer]
  • A. TAG Heuer chosen
    TAG Heuer is a Swiss luxury watchmaker renowned for its high-end mechanical and connected timepieces that blend traditional craftsmanship with modern technology.
  • B. Oris
    Oris is the given name of O.P. Van Sweringen, one of the Van Sweringen brothers known for their influential real estate and railroad developments in early 20th-century Cleveland, Ohio.
  • C. Longines
    Longines is a Swiss luxury watchmaker renowned for its elegant timepieces and long-standing association with equestrian sports and precision timekeeping.
  • D. Ulysse Nardin
    Ulysse Nardin is a Swiss luxury watchmaker renowned for its high-end marine chronometers and innovative horological complications.
  • E. Chronomaster
    Chronomaster is a Zenith watch collection renowned for its high-precision chronographs that blend classic design with advanced mechanical innovation.
  • 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_69d85a0491ec8190830960be8fafb994 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00551521c8190b48d1a074bb4bdfc completed April 15, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fedd24523081908cf12a5d6bdd634d completed May 9, 2026, 7:07 a.m.
Created at: April 10, 2026, 3:05 a.m.