Triple

T14388644
Position Surface form Disambiguated ID Type / Status
Subject ARMv7-A E356786 entity
Predicate supports P516 FINISHED
Object ARM instruction set E13771 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: ARM instruction set | Statement: [ARMv7-A, supports, ARM instruction set]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ARM instruction set
Context triple: [ARMv7-A, supports, ARM instruction set]
  • A. 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.
  • B. ARM
    ARM is the station code used to identify Plaza de Armas station within its transit network.
  • C. ARM
    ARM is the station code used to identify Armidale railway station in New South Wales, Australia, within railway timetabling and ticketing systems.
  • D. ARM
    ARM is the three-letter International Olympic Committee country code representing Armenia in the Olympic Games.
  • E. ARM
    ARM is the National Rail station code for Armadale railway station in West Lothian, Scotland.
  • 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_69de90283b9c8190b50d30ad58bfe085 completed April 14, 2026, 7:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd551623608190ba1de09b423cc5e1 completed May 8, 2026, 3:14 a.m.
Created at: April 10, 2026, 1:16 a.m.