Triple
T25654683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feludar Goendagiri |
E643199
|
entity |
| Predicate | fictionalDetectiveIntroduced |
P32604
|
FINISHED |
| Object | Feluda |
—
|
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 | Statement: [Feludar Goendagiri, fictionalDetectiveIntroduced, Feluda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalDetectiveIntroduced Context triple: [Feludar Goendagiri, fictionalDetectiveIntroduced, Feluda]
-
A.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
B.
fictionalDetective
chosen
Indicates that the subject is a detective character who exists only in fiction rather than in real life.
-
C.
portrayedDetective
Indicates that one entity has played or depicted a detective character in a performance or work.
-
D.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
E.
hasClericalDetective
Indicates that an entity includes or is associated with a detective who is also a member of the clergy.
- 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_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 6:31 p.m.