Triple

T26681132
Position Surface form Disambiguated ID Type / Status
Subject Franco-Russian Military Convention of 1892 E672613 entity
Predicate typeOfCommitment P27619 FINISHED
Object mutual defense obligation 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: mutual defense obligation | Statement: [Franco-Russian Military Convention of 1892, typeOfCommitment, mutual defense obligation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfCommitment
Context triple: [Franco-Russian Military Convention of 1892, typeOfCommitment, mutual defense obligation]
  • A. typicalCommitment
    Indicates a standard or commonly expected level of obligation or promise that one entity holds toward another or toward performing an action.
  • B. coreCommitment
    Indicates a fundamental, central obligation or promise that defines the primary responsibility or dedication within a relationship or agreement.
  • C. commitmentGrade chosen
    Indicates the level or quality of commitment one entity has made toward another entity or agreed-upon action.
  • D. commitment
    Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
  • E. typeOfTrust
    Indicates the specific kind or category of trust that characterizes the relationship between entities.
  • 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_69eecda13424819092b17942c4edf722 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69fd0d0ba5c48190bddb3f0e6637544c completed May 7, 2026, 10:07 p.m.
PD Predicate disambiguation batch_69fd0c4324a8819086c90adf46216e0e completed May 7, 2026, 10:03 p.m.
Created at: April 27, 2026, 3:20 a.m.