Triple
T21423950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore 1541 |
E528504
|
entity |
| Predicate | hasDataTransferMethod |
P5991
|
FINISHED |
| Object | serial bit-banged protocol |
—
|
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: serial bit-banged protocol | Statement: [Commodore 1541, hasDataTransferMethod, serial bit-banged protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataTransferMethod Context triple: [Commodore 1541, hasDataTransferMethod, serial bit-banged protocol]
-
A.
hasDropType
Indicates that an entity is associated with a specific type or category of drop (e.g., item, reward, or resource obtained).
-
B.
dataTransferType
chosen
Indicates the method or mode by which data is transmitted or exchanged between entities.
-
C.
canBeAirDropped
Indicates that an item or entity is suitable to be delivered or deployed by being dropped from an aircraft.
-
D.
dragType
Indicates the manner or category of dragging interaction that occurs between entities.
-
E.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813b798c8190a379cbf6cc6e14d2 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.