Triple

T493738
Position Surface form Disambiguated ID Type / Status
Subject Iwakura Mission E10243 entity
Predicate treatyRevisionOutcome P14166 FINISHED
Object failed to achieve immediate treaty revision 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: failed to achieve immediate treaty revision | Statement: [Iwakura Mission, treatyRevisionOutcome, failed to achieve immediate treaty revision]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: treatyRevisionOutcome
Context triple: [Iwakura Mission, treatyRevisionOutcome, failed to achieve immediate treaty revision]
  • A. treaty
    Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
  • B. treatyAlsoKnownAs
    Indicates that a treaty is referred to by an alternative name or alias.
  • C. mergedByTreaty
    Indicates that two or more entities were combined into a single entity as a result of a formal treaty or agreement.
  • D. cededByTreaty
    Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
  • E. treatyEnteredIntoForce
    Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
  • 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_69a2e847df8481909239ec08ccf1e376 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f0fbfa408190aeb3b93996a35c00 completed Feb. 28, 2026, 1:43 p.m.
PD Predicate disambiguation batch_69a2edf90ca88190b6a182e5b6733612 completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2eebb2c908190960a4d0c014304cd completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.