Triple
T2903284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interpreter of Maladies |
E62699
|
entity |
| Predicate | hasMainCharactersFrom |
P29709
|
FINISHED |
| Object | Indian diaspora |
—
|
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: Indian diaspora | Statement: [Interpreter of Maladies, hasMainCharactersFrom, Indian diaspora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCharactersFrom Context triple: [Interpreter of Maladies, hasMainCharactersFrom, Indian diaspora]
-
A.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
B.
featuresCharactersFrom
chosen
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
C.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
D.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
E.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
- 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe0b5546c8190852d9a454e41eee6 |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:10 p.m.