Triple
T14388867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arm |
E356790
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | ARM Holdings |
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 Holdings | Statement: [Arm, alsoKnownAs, ARM Holdings]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ARM Holdings Context triple: [Arm, alsoKnownAs, ARM Holdings]
-
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 three-letter International Olympic Committee country code representing Armenia in the Olympic Games.
-
C.
ARM
ARM is the station code used to identify Plaza de Armas station within its transit network.
-
D.
ARM
ARM is the station code used to identify Armidale railway station in New South Wales, Australia, within railway timetabling and ticketing systems.
-
E.
ARM
ARM is a South African diversified mining and minerals company involved in the exploration and production of commodities such as iron ore, manganese, coal, copper, and platinum group metals.
- 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_69de9029ef048190bdda5ee41618e720 |
completed | April 14, 2026, 7:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd648409f48190b099cd137879487e |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:16 a.m.