Triple
T23969968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarrainodu |
E604200
|
entity |
| Predicate | hasItemInFranchise |
P154078
|
FINISHED |
| Object | dubbed Hindi 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: dubbed Hindi version | Statement: [Sarrainodu, hasItemInFranchise, dubbed Hindi version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasItemInFranchise Context triple: [Sarrainodu, hasItemInFranchise, dubbed Hindi version]
-
A.
includedInFranchise
Indicates that an entity is part of, or belongs to, a larger franchise or franchise series.
-
B.
usedByFranchise
Indicates that something (such as a resource, asset, or element) is utilized or employed by a particular franchise.
-
C.
hasFranchiseRepresentation
Indicates that one entity serves as an official franchise representative or outlet for another entity.
-
D.
hasParentFranchise
Indicates that one franchise entity is the parent or overarching franchise of another franchise entity.
-
E.
includedFranchise
Indicates that one franchise is contained within, or forms part of, another franchise.
- 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_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. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:25 p.m.