Triple
T34622919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Power Macintosh 7600 |
E889054
|
entity |
| Predicate | videoOut |
P83205
|
FINISHED |
| Object | Apple video output port |
—
|
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: Apple video output port | Statement: [Apple Power Macintosh 7600, videoOut, Apple video output port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoOut Context triple: [Apple Power Macintosh 7600, videoOut, Apple video output port]
-
A.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
B.
videoOutputConnector
chosen
Indicates a relationship where a device or component provides a connector used to output video signals to an external display or receiver.
-
C.
videoIn
Indicates that one entity is a video that is contained within, embedded in, or associated as input to another entity.
-
D.
rawVideoOutput
Indicates that an entity produces or provides unprocessed, uncompressed, or minimally processed video signal as output.
-
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.
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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 2:04 a.m.