Triple
T9183314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 68020 |
E220388
|
entity |
| Predicate | supportsAddressSpace |
P3700
|
FINISHED |
| Object | 4 GB |
—
|
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: 4 GB | Statement: [Motorola 68020, supportsAddressSpace, 4 GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAddressSpace Context triple: [Motorola 68020, supportsAddressSpace, 4 GB]
-
A.
supportsByteAddressing
Indicates that one entity provides the capability for direct access to individual bytes within its addressable memory or data space for another entity.
-
B.
addressSpaceSize
chosen
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
C.
supportsAddressTypes
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
-
D.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
E.
supportsLogicalBlockAddressing
Indicates that one entity provides or is compatible with logical block addressing functionality for another entity or operation.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc2553e548190898434aeda517407 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.