Triple

T28943811
Position Surface form Disambiguated ID Type / Status
Subject O3 E730525 entity
Predicate hasBreak P56828 FINISHED
Object 2019-10-01 to 2019-11-01 (approximate commissioning break) 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: 2019-10-01 to 2019-11-01 (approximate commissioning break) | Statement: [O3, hasBreak, 2019-10-01 to 2019-11-01 (approximate commissioning break)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBreak
Context triple: [O3, hasBreak, 2019-10-01 to 2019-11-01 (approximate commissioning break)]
  • A. breaksWith
    Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
  • B. breaksOver
    Indicates that one entity moves or crashes forcefully onto the surface or boundary of another entity, typically dispersing or shattering upon contact.
  • C. hasBreakOfGaugeWith
    Indicates that two connected railway lines or networks meet at a point where their track gauges differ, requiring a change of trains or transfer of cargo.
  • D. breaksOn
    Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from another entity.
  • E. breakType chosen
    Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
  • 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_69f043ea0aa88190a25acbf46157995a completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f6c49627908190b3553474c7c3072b completed May 3, 2026, 3:44 a.m.
PD Predicate disambiguation batch_69f6c3f23ae081909a52801266063a3c completed May 3, 2026, 3:41 a.m.
Created at: April 28, 2026, 8:38 a.m.