Triple

T16269932
Position Surface form Disambiguated ID Type / Status
Subject Common Article 1 E394971 entity
Predicate coreObligation P122454 FINISHED
Object to respect the Geneva Conventions 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: to respect the Geneva Conventions | Statement: [Common Article 1, coreObligation, to respect the Geneva Conventions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coreObligation
Context triple: [Common Article 1, coreObligation, to respect the Geneva Conventions]
  • A. obligation
    Indicates that one entity is bound or required to perform a duty, action, or fulfill a condition toward another entity or according to a rule or agreement.
  • B. obligationCondition
    Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
  • C. hasObligationLevel
    Indicates that one entity bears a specified degree or intensity of duty, responsibility, or required action toward another entity or situation.
  • D. obligationType
    Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
  • E. monitorsObligationsOf
    Indicates that one entity oversees, tracks, or checks another entity’s duties or required actions to ensure they are fulfilled.
  • 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_69d87f221d8081909b0b2063e7528ba2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24608dd20819082f46a64af233038 completed April 17, 2026, 2:39 p.m.
PD Predicate disambiguation batch_69e219f259e88190bf49d8408c04178e completed April 17, 2026, 11:30 a.m.
PDg Predicate description generation batch_69e21e56e0348190a3d9475360231a70 completed April 17, 2026, 11:49 a.m.
Created at: April 10, 2026, 5:05 a.m.