Triple

T743475
Position Surface form Disambiguated ID Type / Status
Subject Locarno Era E15290 entity
Predicate endedDueTo P18909 FINISHED
Object growing German dissatisfaction with Versailles settlement 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: growing German dissatisfaction with Versailles settlement | Statement: [Locarno Era, endedDueTo, growing German dissatisfaction with Versailles settlement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endedDueTo
Context triple: [Locarno Era, endedDueTo, growing German dissatisfaction with Versailles settlement]
  • A. postponementReason
    Indicates the reason or cause for which an event, action, or decision has been delayed or rescheduled.
  • B. hasDeadline
    Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
  • C. endedWith
    Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
  • D. adjournedFor
    Indicates that an event, meeting, or proceeding has been paused or suspended for a specified duration or until a particular time or condition is met.
  • E. endedConflict
    Indicates that a previously ongoing conflict between entities has been brought to an end.
  • 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_69a49358aa308190adbc9b5a0a2adcf9 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a60f92d08190a4f44c5b4d068ab5 completed March 1, 2026, 8:48 p.m.
PD Predicate disambiguation batch_69a4a4fdaaf48190985f62acfc069508 completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a5a35c68819082429755c046e9a7 completed March 1, 2026, 8:46 p.m.
Created at: March 1, 2026, 7:37 p.m.