Triple
T37163919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VobSub |
E920744
|
entity |
| Predicate | subtitleSynchronization |
P187491
|
FINISHED |
| Object | time-based |
—
|
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: time-based | Statement: [VobSub, subtitleSynchronization, time-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subtitleSynchronization Context triple: [VobSub, subtitleSynchronization, time-based]
-
A.
subtitleDFunction
Indicates a functional relationship where one entity serves as the subtitle or secondary textual label for another entity.
-
B.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
C.
subtitleRequirement
Indicates that one entity specifies whether subtitles are required, optional, or not needed in relation to another entity (such as media content or a viewing context).
-
D.
hasSubtitles
Indicates that one media item provides subtitle text or tracks that accompany another media item or its audio content.
-
E.
subtitlePolicy
Indicates a policy or rule governing how subtitles are handled, such as their presence, format, language, or display conditions.
- 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_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. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.