Triple
T1923094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM System/370 |
E40167
|
entity |
| Predicate | addressWidth |
P33191
|
FINISHED |
| Object | 24-bit |
—
|
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: 24-bit | Statement: [IBM System/370, addressWidth, 24-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressWidth Context triple: [IBM System/370, addressWidth, 24-bit]
-
A.
addressLength
Indicates the length or number of characters in an address.
-
B.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
C.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
D.
streetAddressRange
Indicates the span of street address numbers (e.g., from a minimum to a maximum) that are associated with a particular street segment or location.
-
E.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
- F. None of above. chosen
Provenance (4 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb23459ac819088ded5bfac9d4aad |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.