Triple
T21424067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore VIC-20 |
E528506
|
entity |
| Predicate | primaryOutputDevice |
P19792
|
FINISHED |
| Object | television |
—
|
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: television | Statement: [Commodore VIC-20, primaryOutputDevice, television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOutputDevice Context triple: [Commodore VIC-20, primaryOutputDevice, television]
-
A.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
B.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
C.
primaryInputOutput
Indicates that one entity serves as the main source or destination of data, signals, or materials for another entity within a process or system.
-
D.
primaryDeviceCategory
chosen
Indicates the main type or class of device associated with an entity or event, distinguishing it from other possible device categories.
-
E.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system or context.
- 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.