Triple
T27582415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCI bus |
E699615
|
entity |
| Predicate | configurationSpaceSizePerDevice |
P167781
|
FINISHED |
| Object | 256 bytes in conventional PCI |
—
|
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: 256 bytes in conventional PCI | Statement: [PCI bus, configurationSpaceSizePerDevice, 256 bytes in conventional PCI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationSpaceSizePerDevice Context triple: [PCI bus, configurationSpaceSizePerDevice, 256 bytes in conventional PCI]
-
A.
maximumDevicesPerChannel
Indicates the highest number of devices that are allowed to be associated with or operate on a single channel.
-
B.
maxDevicesPerChannel
Indicates the maximum number of devices that are allowed to be associated with or operate on a single channel.
-
C.
keySpaceSize
Indicates the total number of distinct keys that can exist within a given key space or key domain.
-
D.
supportsDeviceCount
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
-
E.
dimensionOfConfigurationSpace
Indicates the number of independent parameters or degrees of freedom that define the configuration space of a system.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 2:03 p.m.