Triple
T34622917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Power Macintosh 7600 |
E889054
|
entity |
| Predicate | videoIn |
P180387
|
FINISHED |
| Object | composite video input |
—
|
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: composite video input | Statement: [Apple Power Macintosh 7600, videoIn, composite video input]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoIn Context triple: [Apple Power Macintosh 7600, videoIn, composite video input]
-
A.
videoType
Indicates the classification or category of a video (such as format, genre, or purpose) associated with an entity.
-
B.
isVideoOf
Indicates that one entity is a video recording or representation depicting, documenting, or illustrating the other entity.
-
C.
videoPlatform
Indicates a relationship where an entity serves as or is associated with a platform used for hosting, sharing, or streaming video content.
-
D.
videoFeatures
Indicates that one entity possesses or includes specific characteristics, attributes, or elements of a video.
-
E.
homeVideo
Indicates that an entity is a video recording made in a domestic or personal setting, typically by non-professionals for private use.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f73b731ec881908f3e4d5e97d31908 |
completed | May 3, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69f73a3a5d008190971cbde33409682b |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73b72691481908a79ac4e4e9d8d51 |
completed | May 3, 2026, 12:11 p.m. |
Created at: May 1, 2026, 2:04 a.m.