Triple

T11661359
Position Surface form Disambiguated ID Type / Status
Subject HMS Rawalpindi E277126 entity
Predicate conversionToArmedMerchantCruiser P21289 FINISHED
Object 1939 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: 1939 | Statement: [HMS Rawalpindi, conversionToArmedMerchantCruiser, 1939]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conversionToArmedMerchantCruiser
Context triple: [HMS Rawalpindi, conversionToArmedMerchantCruiser, 1939]
  • A. conversionOfShip chosen
    Indicates the process by which a ship is altered or transformed from one configuration, role, or specification into another.
  • B. enhancedArmament
    Indicates that an entity’s weaponry or combat equipment has been upgraded, augmented, or otherwise improved beyond its standard configuration.
  • C. 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.
  • D. combatArm
    Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
  • E. rocketArmament
    Indicates that an entity is equipped with or carries rocket-based weaponry as part of its armament.
  • 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_69d6aafbb3c081908a9cdb4ecb8d981d completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a3d29fdc8190af46b6e2badb1df5 completed April 10, 2026, 7:16 a.m.
PD Predicate disambiguation batch_69d88a73f9ac819095662042804bf40a completed April 10, 2026, 5:28 a.m.
Created at: April 8, 2026, 9:39 p.m.