Triple
T32988177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 5154 Enhanced Color Display |
E844004
|
entity |
| Predicate | videoInputConnector |
P180087
|
FINISHED |
| Object | DE-9 |
—
|
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: DE-9 | Statement: [IBM 5154 Enhanced Color Display, videoInputConnector, DE-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoInputConnector Context triple: [IBM 5154 Enhanced Color Display, videoInputConnector, DE-9]
-
A.
videoOutputConnector
Indicates a relationship where a device or component provides a connector used to output video signals to an external display or receiver.
-
B.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
C.
visualDevice
Indicates a relationship where an entity functions as or is associated with a device used for visual display, capture, or processing.
-
D.
odiCapNumber
Indicates the unique sequential cap number assigned to a player for their debut in One Day International (ODI) cricket.
-
E.
videoChip
Indicates a relationship where an entity functions as or contains a video-processing chip or component used for handling video signals or graphics.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: May 1, 2026, 1:22 a.m.