Triple
T28901600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARM SVE |
E732964
|
entity |
| Predicate | vectorLengthRangeBits |
P54172
|
FINISHED |
| Object | 128–2048 |
—
|
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: 128–2048 | Statement: [ARM SVE, vectorLengthRangeBits, 128–2048]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vectorLengthRangeBits Context triple: [ARM SVE, vectorLengthRangeBits, 128–2048]
-
A.
vectorLength
Indicates the numerical magnitude or size of a vector, typically computed from its components.
-
B.
hasLengthRange
chosen
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
-
C.
hasMinimalVectorLength
Indicates that the associated vector has a length (magnitude) that meets or exceeds a specified minimal threshold.
-
D.
bitWidth
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
E.
hasBodyLengthRange
Indicates the range of possible body lengths associated with an entity, typically expressed as a minimum and maximum value.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa8deec8190b1eef143e10c9598 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:03 a.m.