Triple

T15683781
Position Surface form Disambiguated ID Type / Status
Subject Takao class E377643 entity
Predicate designedForTreaty P119743 FINISHED
Object Washington Naval Treaty limits 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: Washington Naval Treaty limits | Statement: [Takao class, designedForTreaty, Washington Naval Treaty limits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForTreaty
Context triple: [Takao class, designedForTreaty, Washington Naval Treaty limits]
  • A. treatySignedFor
    Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
  • B. designTreaty
    Indicates the action or relationship of creating, drafting, or formulating the terms and structure of a treaty between parties.
  • C. treatyOf
    Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
  • D. treaty
    Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
  • E. treatyType
    Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
  • 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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04f31b5b881908e46ecd9fc6048ab completed April 16, 2026, 2:53 a.m.
PD Predicate disambiguation batch_69deda8c856c8190882330114f9a1a5f completed April 15, 2026, 12:23 a.m.
PDg Predicate description generation batch_69dff7f3016c8190ac68d76e65e07af4 completed April 15, 2026, 8:41 p.m.
Created at: April 10, 2026, 4:17 a.m.