Triple
T26377297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 4040 |
E660933
|
entity |
| Predicate | bitSerialOrParallel |
P160475
|
FINISHED |
| Object | 4-bit parallel |
—
|
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: 4-bit parallel | Statement: [Intel 4040, bitSerialOrParallel, 4-bit parallel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitSerialOrParallel Context triple: [Intel 4040, bitSerialOrParallel, 4-bit parallel]
-
A.
serialInterface
Indicates a relationship where data is transmitted between components over a serial communication interface (one bit at a time over a communication line or bus).
-
B.
hasSerialInputPin
Indicates that an entity possesses a pin or connector specifically designated for receiving serial input signals.
-
C.
hasSerialOutputPin
Indicates that an entity is equipped with a pin or connector dedicated to transmitting data via a serial output interface.
-
D.
serialProperty
Indicates that one entity is a property or attribute that is part of a sequential or ordered series associated with another entity.
-
E.
serialModeDescription
Indicates the description or textual explanation of a device’s serial communication mode or configuration.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61071a4c4819090729e0c9789cf21 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:02 p.m.