Triple
T21644275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPC664 |
E534174
|
entity |
| Predicate | supportsCassette |
P145360
|
FINISHED |
| Object | via external cassette unit |
—
|
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: via external cassette unit | Statement: [CPC664, supportsCassette, via external cassette unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCassette Context triple: [CPC664, supportsCassette, via external cassette unit]
-
A.
cassetteTypeSupported
Indicates that a given system, device, or component is compatible with and can operate using a specified cassette type.
-
B.
hasIntegratedCassetteDeck
Indicates that one object includes a built-in cassette deck as part of its overall unit or structure.
-
C.
cassetteWidth
Indicates the measurement of how wide a cassette is along its horizontal dimension.
-
D.
hasCassetteDataRate
Indicates the data transfer rate associated with a cassette in the context of the described relationship or system.
-
E.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5393ed388190a0bc385de2b861bf |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:35 p.m.