Triple

T6446961
Position Surface form Disambiguated ID Type / Status
Subject Article II (Boundary Waters Treaty of 1909) E138365 entity
Predicate cameIntoForceWithTreatyOn P11446 FINISHED
Object 1910-05-05 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: 1910-05-05 | Statement: [Article II (Boundary Waters Treaty of 1909), cameIntoForceWithTreatyOn, 1910-05-05]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cameIntoForceWithTreatyOn
Context triple: [Article II (Boundary Waters Treaty of 1909), cameIntoForceWithTreatyOn, 1910-05-05]
  • A. treatyEnteredIntoForce chosen
    Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
  • B. treatySignedFor
    Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
  • C. treatyOf
    Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
  • 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. treatySignedWith
    Indicates that a formal treaty or agreement has been officially signed between two parties.
  • 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_69c008aa61ac8190bc96715ed79fe2d8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0698edeac81909426902471d8a57b completed March 22, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69c0673b44148190aed70084f0ff4992 completed March 22, 2026, 10:03 p.m.
Created at: March 22, 2026, 4:46 p.m.