Triple
T25235447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVV Entertainment |
E632323
|
entity |
| Predicate | RRRReleaseType |
P3286
|
FINISHED |
| Object | pan-Indian release |
—
|
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: pan-Indian release | Statement: [DVV Entertainment, RRRReleaseType, pan-Indian release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RRRReleaseType Context triple: [DVV Entertainment, RRRReleaseType, pan-Indian release]
-
A.
theatricalReleaseType
Indicates the manner or category of a work’s release in theaters, such as wide, limited, or special event distribution.
-
B.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
C.
mannerOfRelease
Indicates the way or method by which something is released or let go (e.g., physically, chemically, or procedurally).
-
D.
theatricalReleaseWith
Indicates that two or more entities share the same theatrical release context, such as being released together or as part of the same theatrical event or distribution.
-
E.
theatricalReleaseIn
Indicates that a film or performance was released or shown theatrically in a specified location or market.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df954cc8190ab223daad550fd0d |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:07 p.m.