Triple
T26377228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCS-4 |
E660932
|
entity |
| Predicate | hasShiftRegister |
P165342
|
FINISHED |
| Object | Intel 4003 |
—
|
NE NERFINISHED |
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: Intel 4003 | Statement: [MCS-4, hasShiftRegister, Intel 4003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShiftRegister Context triple: [MCS-4, hasShiftRegister, Intel 4003]
-
A.
hasSerialInputPin
Indicates that an entity possesses a pin or connector specifically designated for receiving serial input signals.
-
B.
hasSerialOutputPin
Indicates that an entity is equipped with a pin or connector dedicated to transmitting data via a serial output interface.
-
C.
hasClockInput
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
D.
numberOfRegisters
Indicates the total count of registers associated with or contained in a given entity.
-
E.
hasStandardRegister
Indicates that something is expressed or occurs in a standard, neutral, or non-marked linguistic register.
- 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_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 26, 2026, 11:02 p.m.