Triple
T21627480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZX81 |
E533739
|
entity |
| Predicate | videoGenerationMethod |
P69703
|
FINISHED |
| Object | software-generated video |
—
|
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: software-generated video | Statement: [ZX81, videoGenerationMethod, software-generated video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoGenerationMethod Context triple: [ZX81, videoGenerationMethod, software-generated video]
-
A.
videoDesigner
Indicates a relationship where one entity is responsible for designing or creating the visual and structural elements of a video for another entity or project.
-
B.
musicVideoCoDirector
Indicates a relationship where two or more individuals share responsibility for directing the same music video.
-
C.
generation
Indicates the relationship in which one entity produces, creates, or brings another entity into existence.
-
D.
generationMethod
chosen
Indicates the process, technique, or procedure by which something is created, produced, or derived.
-
E.
videoStyle
Indicates the stylistic characteristics or presentation format applied to a video (such as tone, visual approach, or editing style).
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52141e1c8190a861f4bc7cfcb490 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.