Triple
T23969670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parugu |
E604194
|
entity |
| Predicate | hasDubbedVersion |
P130985
|
FINISHED |
| Object | Veerta – Hindi dubbed version |
—
|
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: Veerta – Hindi dubbed version | Statement: [Parugu, hasDubbedVersion, Veerta – Hindi dubbed version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDubbedVersion Context triple: [Parugu, hasDubbedVersion, Veerta – Hindi dubbed version]
-
A.
dubbedFor
chosen
Indicates that one media work has been voice-dubbed to create a version suitable for another language, region, or audience.
-
B.
languageDubbedIn
Indicates that the content’s audio has been dubbed into the specified language.
-
C.
hasBilingualVersions
Indicates that something exists in two different language versions or forms.
-
D.
hasKoreanVersion
Indicates that something has a corresponding version or counterpart that is in the Korean language.
-
E.
adaptedInLanguage
Indicates that a work or content has been modified or translated so it can be presented or understood in a specified language.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1db392c8190a1044b75b898243a |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.