Triple
T27224728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lalmohan Ganguly |
E681377
|
entity |
| Predicate | writesFictionalDetectiveStories |
P78982
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lalmohan Ganguly, writesFictionalDetectiveStories, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writesFictionalDetectiveStories Context triple: [Lalmohan Ganguly, writesFictionalDetectiveStories, yes]
-
A.
fictionalDetective
Indicates that the subject is a detective character who exists only in fiction rather than in real life.
-
B.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
C.
hasWrittenFiction
chosen
Indicates that one entity is the creator or author of fictional written works associated with another entity.
-
D.
conductsInFiction
Indicates that an entity carries out or performs an action or role within a fictional context or narrative.
-
E.
workInFiction
Indicates that one entity is a fictional work in which the other entity appears or is set.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264a03648190a9b6904ce2f7aeeb |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:44 a.m.