Triple
T1649871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 8088 |
E35665
|
entity |
| Predicate | dataWidthCategory |
P19786
|
FINISHED |
| Object | 8-bit external |
—
|
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 external | Statement: [Intel 8088, dataWidthCategory, 8-bit external]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataWidthCategory Context triple: [Intel 8088, dataWidthCategory, 8-bit external]
-
A.
typicalWidth
chosen
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
B.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
C.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
-
D.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
E.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.