Triple
T17758237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEC Alpha 21264 |
E443300
|
entity |
| Predicate | integerUnits |
P19248
|
FINISHED |
| Object | multiple integer execution units |
—
|
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: multiple integer execution units | Statement: [DEC Alpha 21264, integerUnits, multiple integer execution units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integerUnits Context triple: [DEC Alpha 21264, integerUnits, multiple integer execution units]
-
A.
integerUnit
Indicates that one entity serves as the integer-valued unit or base measurement associated with another entity.
-
B.
isIntegerUnitIn
Indicates that one integer-valued unit is contained within, or belongs to, a specified larger unit or unit set.
-
C.
minorUnitsPerUnit
Indicates the number of smaller sub-units that collectively make up one whole unit in a given measurement or currency system.
-
D.
nativeUnit
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
E.
numberOfUnits
chosen
Indicates the quantity or count of discrete units associated with an entity or relationship.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841fe97881908f4df503fb781763 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.