Triple

T13389016
Position Surface form Disambiguated ID Type / Status
Subject Maxim Integrated E319521 entity
Predicate tradedAs P2822 FINISHED
Object MXIM E319521 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: MXIM | Statement: [Maxim Integrated, tradedAs, MXIM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MXIM
Context triple: [Maxim Integrated, tradedAs, MXIM]
  • A. MXIM chosen
    MXIM is the stock ticker symbol for Maxim Integrated, a former American analog and mixed-signal semiconductor company acquired by Analog Devices.
  • B. MX
    MX is the Montreal Exchange, Canada's primary derivatives exchange specializing in futures and options trading.
  • C. MX
    MX is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Mexico in international standards and systems.
  • D. MX
    MX is a specific trim level designation used for the Mercury Montego sedan, denoting a particular configuration of features and equipment.
  • E. MX
    MX is the IATA airline designator assigned to Breeze Airways, a U.S.-based low-cost carrier.
  • 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_69d806b886bc8190b676e7768b8e01c5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dba0d3a40081909ba49556130ad0e7 completed April 12, 2026, 1:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7306df34c81909f2ad5b753b7fb7f completed May 3, 2026, 11:24 a.m.
Created at: April 9, 2026, 9:34 p.m.