Triple
T14014565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Famine in Greece |
E337171
|
entity |
| Predicate | notableDeathTollEstimate |
P700
|
FINISHED |
| Object | over 300000 deaths |
—
|
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: over 300000 deaths | Statement: [Great Famine in Greece, notableDeathTollEstimate, over 300000 deaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeathTollEstimate Context triple: [Great Famine in Greece, notableDeathTollEstimate, over 300000 deaths]
-
A.
deathTollEstimate
chosen
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
B.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
C.
casualtiesEstimate
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
-
D.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
E.
deathTollRanking
Indicates the relative position of an event or entity when ordered by the number of deaths it caused, typically from highest to lowest.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.