Triple

T6071015
Position Surface form Disambiguated ID Type / Status
Subject Ems Dispatch crisis E135279 entity
Predicate manipulationType P38005 FINISHED
Object editing and shortening of the original telegram 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: editing and shortening of the original telegram | Statement: [Ems Dispatch crisis, manipulationType, editing and shortening of the original telegram]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: manipulationType
Context triple: [Ems Dispatch crisis, manipulationType, editing and shortening of the original telegram]
  • A. adjustmentType
    Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
  • B. changeType chosen
    Indicates the specific kind or category of modification that has occurred to an entity or relationship.
  • C. operationType
    Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
  • D. modeType
    Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
  • E. tractionType
    Indicates the type or method of traction applied or used in relation to an entity or system.
  • 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_69c00879e8048190b690717d19c5bc03 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05758a21c81909cc10ef5f725a489 completed March 22, 2026, 8:55 p.m.
PD Predicate disambiguation batch_69c049f21fe08190995df3c5c05fb8ea completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:10 p.m.