Triple
T272512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM PC |
E5665
|
entity |
| Predicate | busWidth |
P4121
|
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: [IBM PC, busWidth, 8-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busWidth Context triple: [IBM PC, busWidth, 8-bit]
-
A.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
B.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
C.
maximumDevicesPerBus
Indicates the maximum number of devices that are allowed to be connected to a single bus.
-
D.
maxDevicesPerBus
Indicates the maximum number of devices that are allowed to be connected to a single bus.
-
E.
hasBusArbitration
Indicates that one entity manages or participates in the control and coordination of access to a shared communication bus among multiple entities.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dcf667c8190a7b8630fe67b9a90 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.