Triple

T4035862
Position Surface form Disambiguated ID Type / Status
Subject Type 26 frigate E83824 entity
Predicate navyRole P9463 FINISHED
Object core element of future Royal Navy surface fleet 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: core element of future Royal Navy surface fleet | Statement: [Type 26 frigate, navyRole, core element of future Royal Navy surface fleet]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: navyRole
Context triple: [Type 26 frigate, navyRole, core element of future Royal Navy surface fleet]
  • A. navy
    Indicates that an entity serves as or is associated with a nation's naval military force.
  • B. navalTacticRole
    Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
  • C. militaryRole chosen
    Indicates the specific function, position, or duty an entity holds within a military organization or context.
  • D. navalRankContext
    Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
  • E. navalSupportCommander
    Indicates a relationship where one entity serves as the commander responsible for directing or overseeing naval support operations for another entity or mission.
  • 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_69aed92f7cf0819098e0539bdcc3767f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb132f6c8190937acd35a6a5a9e4 completed March 9, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69aef8fe440c819093a7fa22c4ff3f1a completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:36 p.m.