Triple

T20629318
Position Surface form Disambiguated ID Type / Status
Subject ARM7TDMI E506908 entity
Predicate designer P184 FINISHED
Object ARM Holdings NE NERFINISHED

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: ARM Holdings | Statement: [ARM7TDMI, designer, ARM Holdings]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ARM Holdings
Context triple: [ARM7TDMI, designer, ARM Holdings]
  • A. Imagination Technologies
    Imagination Technologies is a British semiconductor and software design company best known for its PowerVR graphics processing units used in mobile and embedded devices.
  • B. ARM chosen
    ARM is a family of energy-efficient RISC processor architectures widely used in mobile devices, embedded systems, and increasingly in laptops and servers.
  • C. ARM
    ARM is the three-letter International Olympic Committee country code representing Armenia in the Olympic Games.
  • D. ARM
    ARM is the station code used to identify Plaza de Armas station within its transit network.
  • E. ARM
    ARM is the station code used to identify Armidale railway station in New South Wales, Australia, within railway timetabling and ticketing systems.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4bd4a0081908d4e97a590a33fb2 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6abe771e88190a48471bf83b4804d completed April 20, 2026, 10:42 p.m.
Created at: April 16, 2026, 11:42 a.m.