Triple

T27334941
Position Surface form Disambiguated ID Type / Status
Subject HMS Caesar E689915 entity
Predicate navalPowerContext P163920 FINISHED
Object British–French naval rivalry 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: British–French naval rivalry | Statement: [HMS Caesar, navalPowerContext, British–French naval rivalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: navalPowerContext
Context triple: [HMS Caesar, navalPowerContext, British–French naval rivalry]
  • A. navalPowerType
    Indicates the classification of a naval force or capability according to its type or role within maritime power structures.
  • B. navalPowerStatus
    Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
  • C. navalRatioPowers
    Indicates the comparative balance of naval strength or power between entities, typically expressed as a ratio.
  • D. navalPolicy
    Indicates the policies, strategies, or regulatory stance a state or authority adopts regarding the organization, deployment, and use of its naval forces.
  • E. navalCountry
    Indicates that a country possesses or operates a navy, signifying its involvement in naval or maritime military activities.
  • 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_69ef355e5b388190a8fc1eba9b4a6656 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f6416fbf4081909b0913c337927fc4 completed May 2, 2026, 6:24 p.m.
PD Predicate disambiguation batch_69f63c663be481908f233d25d28713a4 completed May 2, 2026, 6:03 p.m.
PDg Predicate description generation batch_69f63fd4f7448190930c723ba7cfce62 completed May 2, 2026, 6:17 p.m.
Created at: April 27, 2026, 11:40 a.m.