Triple
T28900026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Versa Module Europa bus |
E732927
|
entity |
| Predicate | supportsDataWidth |
P177997
|
FINISHED |
| Object | 8‑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: 8‑bit | Statement: [Versa Module Europa bus, supportsDataWidth, 8‑bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataWidth Context triple: [Versa Module Europa bus, supportsDataWidth, 8‑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.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
C.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
D.
supportsLinkWidth
Indicates that one entity is capable of accommodating or enabling a specified width for a link or connection between components.
-
E.
availableWidth
Indicates the amount of horizontal space that is currently free or usable within a given context or container.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a021f84715881908e25b6548e7cf62e |
completed | May 11, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_6a021739b7288190a4ca94c04074c78a |
completed | May 11, 2026, 5:51 p.m. |
Created at: April 28, 2026, 8:02 a.m.