Triple

T282907
Position Surface form Disambiguated ID Type / Status
Subject Israeli new shekel E5826 entity
Predicate introducedToCombat P9074 FINISHED
Object hyperinflation of old shekel 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: hyperinflation of old shekel | Statement: [Israeli new shekel, introducedToCombat, hyperinflation of old shekel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedToCombat
Context triple: [Israeli new shekel, introducedToCombat, hyperinflation of old shekel]
  • A. mainCombatant
    Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
  • B. usedInBattle
    Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
  • C. usedWarfareType
    Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
  • D. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • E. battledIn
    Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
  • 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_69a25946a7ac8190a78871c210213272 completed Feb. 28, 2026, 2:56 a.m.
NER Named-entity recognition batch_69a25e0c14b48190a5c936bab36180b3 completed Feb. 28, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69a25b795a6c8190944d48e8418e0ccd completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a25c4b773c81908f1017f40b0bfd07 completed Feb. 28, 2026, 3:08 a.m.
Created at: Feb. 28, 2026, 3:02 a.m.