Triple
T25654981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baksho Rahashya |
E643207
|
entity |
| Predicate | characterRoleOfFeluda |
P23263
|
FINISHED |
| Object | private detective |
—
|
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: private detective | Statement: [Baksho Rahashya, characterRoleOfFeluda, private detective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRoleOfFeluda Context triple: [Baksho Rahashya, characterRoleOfFeluda, private detective]
-
A.
featuresCharacterRole
chosen
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
B.
roleInMurderOnTheOrientExpress
Indicates the specific involvement or function an entity has within the context of the murder case in "Murder on the Orient Express."
-
C.
roleInMysteryMen
Indicates that one entity has a specific role or part in the context of "Mystery Men," such as in its story, production, or related work.
-
D.
roleInFamousPlay
Indicates that an entity portrays or has portrayed a specific character in a well-known theatrical play.
-
E.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
- 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_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 6:32 p.m.