Triple
T21832332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOS Technology VIC-II |
E539027
|
entity |
| Predicate | NTSCVariantPartNumber |
P145474
|
FINISHED |
| Object | 6567 |
—
|
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: 6567 | Statement: [MOS Technology VIC-II, NTSCVariantPartNumber, 6567]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NTSCVariantPartNumber Context triple: [MOS Technology VIC-II, NTSCVariantPartNumber, 6567]
-
A.
televisionSystemType
Indicates the type or category of television system associated with an entity (e.g., analog, digital, cable, satellite).
-
B.
backwardsCompatibleWithATSC1.0Receivers
Indicates that something can operate correctly with and be received or decoded by ATSC 1.0-compatible receivers without requiring modifications to those receivers.
-
C.
televisionFormat
Indicates the specific type or style of television program or production format associated with an entity.
-
D.
intendedCartridgeStandard
Indicates that an item is designed to be used with, or conform to, a particular cartridge standard.
-
E.
colorSubcarrierStandard
Indicates the standard or format used for the color subcarrier signal in a video or broadcast system.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a4d2d0819088ded045caeab52d |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 6:55 p.m.