Triple

T31224815
Position Surface form Disambiguated ID Type / Status
Subject Cold War-era Royal Navy E796108 entity
Predicate notableSSBNClass P207377 FINISHED
Object Resolution-class submarine E346680 NE 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: Resolution-class submarine | Statement: [Cold War-era Royal Navy, notableSSBNClass, Resolution-class submarine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableSSBNClass
Context triple: [Cold War-era Royal Navy, notableSSBNClass, Resolution-class submarine]
  • A. submarineClassLeadShip
    Indicates that one entity is the lead (first-built or first-commissioned) ship of a particular submarine class represented by the other entity.
  • B. submarineClassName
    Indicates the specific class designation or type category to which a submarine belongs.
  • C. submarineClassRole
    Indicates the functional role or mission type assigned to a particular class of submarines within a naval context.
  • D. USNDesignation
    Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
  • E. primarySubmarineClassSupported
    Indicates that an entity is designed to support, service, or operate primarily with a specific class of submarines.
  • F. None of above. chosen

Provenance (5 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_69f224da98f88190ab32f690cce5d303 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a296bdfa2f88190a787895f93eaee6d completed June 10, 2026, 1:51 p.m.
PD Predicate disambiguation batch_6a0379e5174c8190a0bdde7e381b7624 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c7ee0388190a29faeb5cdb0950a completed May 12, 2026, 7:16 p.m.
Created at: April 29, 2026, 9:10 p.m.