Triple
T9499045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARMv8-A |
E229087
|
entity |
| Predicate | registerWidthInAArch64 |
P4121
|
FINISHED |
| Object | 64 bits |
—
|
LITERAL 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: 64 bits | Statement: [ARMv8-A, registerWidthInAArch64, 64 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerWidthInAArch64 Context triple: [ARMv8-A, registerWidthInAArch64, 64 bits]
-
A.
extendsRegisterWidthFrom
Indicates that one entity increases or broadens the register width relative to another entity from which it is derived.
-
B.
armSpan
Indicates the distance between an individual's outstretched fingertips, typically measured from one hand to the other across the body.
-
C.
supportsARMv8_5A
Indicates that the subject provides compatibility with, or implements the features of, the ARMv8.5-A architecture.
-
D.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
E.
executionWidth
Indicates the degree of parallelism or number of concurrent units used when executing an operation or process.
- F. None of above.
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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983a94c48190a7ddf95a953c4ecc |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.