Triple

T37667460
Position Surface form Disambiguated ID Type / Status
Subject Action of 23 November 1939 E937858 entity
Predicate GermanShipRole P188525 FINISHED
Object capital ships on raiding mission 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: capital ships on raiding mission | Statement: [Action of 23 November 1939, GermanShipRole, capital ships on raiding mission]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: GermanShipRole
Context triple: [Action of 23 November 1939, GermanShipRole, capital ships on raiding mission]
  • A. GermanShipFate
    Indicates the ultimate outcome or disposition of a German ship, such as whether it was sunk, captured, scuttled, or otherwise ended its service.
  • B. GermanShipUndamaged
    Indicates that a German ship remains intact and has not sustained damage.
  • C. shipTypeSunk
    Indicates that a particular type of ship has been sunk as a result of some event or action.
  • D. isWarshipOf
    Indicates that a given warship belongs to, is operated by, or is part of the naval forces of a specified country or organization.
  • E. FrenchShipType
    Indicates that something is classified as a type of ship associated with France, such as by origin, design, or service.
  • 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_69f76ed6df7c8190b018e5baea716ceb completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaa19e4a88190b04f26c0d4e708fd completed May 6, 2026, 8:52 p.m.
PD Predicate disambiguation batch_69fba887821c8190ae93ef1dd389e9c8 completed May 6, 2026, 8:45 p.m.
PDg Predicate description generation batch_69fba9ddef488190b785d332580650f0 completed May 6, 2026, 8:51 p.m.
Created at: May 3, 2026, 4:18 p.m.