Triple

T29571989
Position Surface form Disambiguated ID Type / Status
Subject Rendsburg ferry E753337 entity
Predicate serviceSuspension P124699 FINISHED
Object 2016 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: 2016 | Statement: [Rendsburg ferry, serviceSuspension, 2016]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: serviceSuspension
Context triple: [Rendsburg ferry, serviceSuspension, 2016]
  • A. serviceSuspendedBeyond
    Indicates that a service has been suspended for a duration that exceeds a specified time or threshold.
  • B. platformSuspension
    Indicates that an entity has been temporarily or permanently barred from accessing or using a particular platform or service.
  • C. workSuspensionRequired
    Indicates that a temporary halt or suspension of work activities is mandated under certain conditions.
  • D. officeSuspendedUnder
    Indicates that an individual’s official position or duties are temporarily halted under the authority or jurisdiction of a specified entity or rule.
  • E. suspensionPeriod chosen
    Indicates the time span during which a right, service, or status is temporarily inactive or halted.
  • 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_69f0ef7fcb4881908a933110adb9bda1 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f7516d5b4081908588a6feb541f355 completed May 3, 2026, 1:45 p.m.
PD Predicate disambiguation batch_69f74d40ebb081909daf60623e38f41d completed May 3, 2026, 1:27 p.m.
Created at: April 28, 2026, 5:59 p.m.