Triple
T21570480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPC464 |
E532267
|
entity |
| Predicate | hasCassetteDataRate |
P144294
|
FINISHED |
| Object | approximately 1000 baud |
—
|
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: approximately 1000 baud | Statement: [CPC464, hasCassetteDataRate, approximately 1000 baud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCassetteDataRate Context triple: [CPC464, hasCassetteDataRate, approximately 1000 baud]
-
A.
cassetteTypeSupported
Indicates that a given system, device, or component is compatible with and can operate using a specified cassette type.
-
B.
cassetteWidth
Indicates the measurement of how wide a cassette is along its horizontal dimension.
-
C.
cassetteHeight
Indicates the vertical dimension or elevation associated with a cassette relative to a reference point or system.
-
D.
hasCartridgeSlot
Indicates that an object includes a dedicated slot or receptacle designed to accept and hold a cartridge.
-
E.
hasPhysicalMedium
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cc5c448190887a836f577d01ba |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.