Triple
T37163912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VobSub |
E920744
|
entity |
| Predicate | isRenderedBy |
P3995
|
FINISHED |
| Object | media player subtitle engine |
—
|
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: media player subtitle engine | Statement: [VobSub, isRenderedBy, media player subtitle engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRenderedBy Context triple: [VobSub, isRenderedBy, media player subtitle engine]
-
A.
isRenderingOf
Indicates that one entity is a visual or graphical depiction or representation of another entity.
-
B.
renderedBy
chosen
Indicates that something is produced, drawn, or visually generated by a particular agent, tool, or process.
-
C.
renderedUnder
Indicates that one entity was produced, displayed, or executed within the authority, context, or environment provided by another entity.
-
D.
canRender
Indicates that one entity has the capability or functionality to generate or display another entity in a visual or presentable form.
-
E.
renders
Indicates that one entity produces, generates, or visually presents another entity, often by transforming data or instructions into a final displayed or usable form.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.