Triple

T8644958
Position Surface form Disambiguated ID Type / Status
Subject Potato War E204749 entity
Predicate hasCasualtiesLevel P84402 FINISHED
Object relatively low compared to contemporary wars 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: relatively low compared to contemporary wars | Statement: [Potato War, hasCasualtiesLevel, relatively low compared to contemporary wars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCasualtiesLevel
Context triple: [Potato War, hasCasualtiesLevel, relatively low compared to contemporary wars]
  • A. casualtiesImpact
    Indicates how the number or severity of casualties affects or influences another factor, situation, or outcome.
  • B. casualtiesIncluded
    Indicates that the referenced count or report of casualties explicitly includes the specified individuals or groups.
  • C. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • D. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • E. casualtiesEstimate
    Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
  • 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_69ca834ca1c88190a11ffb0200342fac completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc479999c881908c0c4e01c07d02d4 completed March 31, 2026, 10:15 p.m.
PD Predicate disambiguation batch_69cc455d6d448190a2da2a319ac78c37 completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc479284a8819099b0b0d879af3372 completed March 31, 2026, 10:15 p.m.
Created at: March 30, 2026, 6:28 p.m.