Triple

T3086026
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Portsmouth E64374 entity
Predicate warIndemnity P19678 FINISHED
Object no monetary indemnity paid by Russia to Japan 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: no monetary indemnity paid by Russia to Japan | Statement: [Treaty of Portsmouth, warIndemnity, no monetary indemnity paid by Russia to Japan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: warIndemnity
Context triple: [Treaty of Portsmouth, warIndemnity, no monetary indemnity paid by Russia to Japan]
  • A. warIndemnityAmount chosen
    Indicates the amount of financial compensation required or paid as indemnity as a result of a war or armed conflict.
  • B. imposedWarIndemnityOn
    Indicates that one party required another party to pay financial compensation as a penalty or reparation following a conflict or war.
  • C. warDamage
    Indicates damage that was caused as a direct consequence of war or armed conflict.
  • D. warPrizeOf
    Indicates that one entity is the prize, spoils, or reward obtained as a result of another entity’s involvement in a war or military conflict.
  • E. concludedWar
    Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
  • 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_69ad857bb4c88190a4cf27893fcabed8 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada1eac5548190bee60ea8262c65a8 completed March 8, 2026, 4:20 p.m.
PD Predicate disambiguation batch_69ad9ded78f881908be6fc0fb7c35764 completed March 8, 2026, 4:03 p.m.
Created at: March 8, 2026, 3:03 p.m.