Triple
T20825250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch famine of 1944–45 |
E512680
|
entity |
| Predicate | foodRationLevel |
P141965
|
FINISHED |
| Object | as low as 400–500 kilocalories per day in some areas |
—
|
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: as low as 400–500 kilocalories per day in some areas | Statement: [Dutch famine of 1944–45, foodRationLevel, as low as 400–500 kilocalories per day in some areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodRationLevel Context triple: [Dutch famine of 1944–45, foodRationLevel, as low as 400–500 kilocalories per day in some areas]
-
A.
dailyRationPlanning
Indicates the planning or allocation of daily rations or supplies for entities.
-
B.
foodRationingInHostCountry
Indicates that the host country imposes restrictions or controlled distribution on available food supplies.
-
C.
storesFood
Indicates that one entity keeps or holds food items for future use or consumption.
-
D.
commonlyConsumedAt
Indicates that one entity is typically eaten or drunk during, or in association with, a particular time, event, or context.
-
E.
foodSold
Indicates that a particular food item is sold or offered for sale by a specific seller or at a specific place.
- F. None of above. chosen
Provenance (4 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fcc60881908ef3d8914d801ea1 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:41 p.m.