Triple
T19991759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Bengal Famine (by P. C. Mahalanobis and others) |
E494079
|
entity |
| Predicate | timePeriodAnalysed |
P58040
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [The Great Bengal Famine (by P. C. Mahalanobis and others), timePeriodAnalysed, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAnalysed Context triple: [The Great Bengal Famine (by P. C. Mahalanobis and others), timePeriodAnalysed, 1943]
-
A.
timePeriodAnalyzed
chosen
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
D.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
-
E.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe10ffc81908c94168b0a8ea9c9 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:31 p.m.