Triple
T25654944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Bengal Rahasya |
E643206
|
entity |
| Predicate | hasProtagonistAssistant |
P8706
|
FINISHED |
| Object | Topshe |
—
|
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: Topshe | Statement: [Royal Bengal Rahasya, hasProtagonistAssistant, Topshe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistAssistant Context triple: [Royal Bengal Rahasya, hasProtagonistAssistant, Topshe]
-
A.
hasProtagonist
chosen
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasSpiritProtagonist
Indicates that the primary or central character in a narrative is a spirit or non-corporeal being.
-
C.
hasProtagonistFromSource
Indicates that a work’s main character originates from, or is derived from, a specified source (such as another work, franchise, or medium).
-
D.
hasSpyProtagonist
Indicates that the main character in the work is a spy or primarily engaged in espionage activities.
-
E.
hasInspectorProtagonist
Indicates that the main character in the work serves in the role of an inspector.
- 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 21, 2026, 6:31 p.m.