Triple
T32986525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM ESA/370 instruction set |
E843960
|
entity |
| Predicate | hasAddressSize |
P3700
|
FINISHED |
| Object | 31 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: 31 bits | Statement: [IBM ESA/370 instruction set, hasAddressSize, 31 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddressSize Context triple: [IBM ESA/370 instruction set, hasAddressSize, 31 bits]
-
A.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
B.
addressSpaceSize
chosen
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
C.
hasWordSize
Indicates that an entity possesses or is characterized by a specific word length or word-based size.
-
D.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
E.
hasAddressRole
Indicates that a specific role or function is associated with an address within a given context (e.g., billing, shipping, primary).
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 1:22 a.m.