Triple
T38404160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCMCIA Type II |
E900976
|
entity |
| Predicate | supportsBusWidth |
P177997
|
FINISHED |
| Object | 16-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: 16-bit | Statement: [PCMCIA Type II, supportsBusWidth, 16-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBusWidth Context triple: [PCMCIA Type II, supportsBusWidth, 16-bit]
-
A.
supportsMemoryBusWidth
chosen
Indicates that one entity is compatible with or able to operate using the specified memory bus width of another entity.
-
B.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
C.
memoryBusWidthBits
Indicates the width, in bits, of the data path used by the memory bus to transfer information.
-
D.
supportedBusInterface
Indicates that one entity provides or is compatible with a particular bus interface used for communication or connection with other components.
-
E.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.