Triple
T8210193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 5160 |
E191793
|
entity |
| Predicate | videoAdapterOptions |
P81512
|
FINISHED |
| Object | MDA |
—
|
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: MDA | Statement: [IBM 5160, videoAdapterOptions, MDA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoAdapterOptions Context triple: [IBM 5160, videoAdapterOptions, MDA]
-
A.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
B.
videoQuality
Indicates the level or standard of clarity, resolution, and overall visual fidelity associated with a given video.
-
C.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
-
D.
videoEncoding
Indicates that one entity is used to encode, compress, or transform video data into a particular digital format or representation for another entity.
-
E.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dd881c8190adcbeb2f33d3295c |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:44 p.m.