Triple
T27582336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISA bus |
E699614
|
entity |
| Predicate | initialWidth |
P167780
|
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: [ISA bus, initialWidth, 8-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialWidth Context triple: [ISA bus, initialWidth, 8-bit]
-
A.
initialBoundingBoxWidth
Indicates the original or starting width value of an object's bounding box before any changes or transformations are applied.
-
B.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
C.
availableWidth
Indicates the amount of horizontal space that is currently free or usable within a given context or container.
-
D.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
E.
sectionWidthGranted
Indicates that a specific width has been allocated or approved for a section within a layout or structure.
- 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.