Triple
T25959242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billa (2009 Telugu film) |
E645490
|
entity |
| Predicate | hasRemakeRelationshipWith |
P131205
|
FINISHED |
| Object | Billa (1980 Telugu film) |
—
|
NE NERFINISHED |
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: Billa (1980 Telugu film) | Statement: [Billa (2009 Telugu film), hasRemakeRelationshipWith, Billa (1980 Telugu film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemakeRelationshipWith Context triple: [Billa (2009 Telugu film), hasRemakeRelationshipWith, Billa (1980 Telugu film)]
-
A.
hasRemakeRelationWith
chosen
Indicates that one work is a remake of, or has been remade as, another work, capturing the remake relationship between the two.
-
B.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
-
C.
hasRemixRelationshipWith
Indicates that one creative work is a remix, reworked version, or derived adaptation of another work.
-
D.
isIndirectRemakeOf
Indicates that one work is a remake of another, but derived through an intermediate adaptation rather than directly from the original.
-
E.
liveActionRemakeOf
Indicates that one work is a live-action remake adaptation of another, originally non-live-action, work.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 22, 2026, 8:47 a.m.