Triple

T36515223
Position Surface form Disambiguated ID Type / Status
Subject Lexington-class battlecruiser E900016 entity
Predicate convertedShip P21289 FINISHED
Object USS Lexington (CV-2) NE NERFINISHED

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: USS Lexington (CV-2) | Statement: [Lexington-class battlecruiser, convertedShip, USS Lexington (CV-2)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: convertedShip
Context triple: [Lexington-class battlecruiser, convertedShip, USS Lexington (CV-2)]
  • A. conversionOfShip chosen
    Indicates the process by which a ship is altered or transformed from one configuration, role, or specification into another.
  • B. componentShip
    Indicates that one entity is a physical or logical component or part of another entity, such that the whole is composed of or depends on that component.
  • C. renamedShipAs
    Indicates that one entity changed the name of a ship to another specified name.
  • D. targetedShip
    Indicates that one entity has selected or designated a particular ship as the focus of its attention or action, such as for attack, tracking, or interaction.
  • E. commissionedShip
    Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
  • 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_69f76e5dada881909da2d34bc7a9202a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: May 3, 2026, 4:10 p.m.