Triple
T25655355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baksho Rahashya (telefilm) |
E643218
|
entity |
| Predicate | originalWorkSeries |
P159914
|
FINISHED |
| Object | Feluda series |
—
|
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: Feluda series | Statement: [Baksho Rahashya (telefilm), originalWorkSeries, Feluda series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalWorkSeries Context triple: [Baksho Rahashya (telefilm), originalWorkSeries, Feluda series]
-
A.
originalWorkForSeries
Indicates that a work serves as the source or initial installment upon which a series is based or from which the series originates.
-
B.
originalSeries
Indicates that one creative work is the initial or primary series from which another related work (such as a sequel, spin-off, or adaptation) originates.
-
C.
originalWorkBy
Indicates that one entity is the creator or originator of another entity (such as a work, idea, or product).
-
D.
relatedWorkSeriesAuthor
Indicates that an author is associated with a work that is part of the same series or a related series as another work.
-
E.
workInAuthorSeries
chosen
Indicates that a work is part of an author-defined series or collection.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 21, 2026, 6:32 p.m.