Triple

T30954000
Position Surface form Disambiguated ID Type / Status
Subject Commander-in-Chief, North Sea Fleet E788621 entity
Predicate isMilitaryRoleIn P9463 FINISHED
Object United Kingdom armed forces 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: United Kingdom armed forces | Statement: [Commander-in-Chief, North Sea Fleet, isMilitaryRoleIn, United Kingdom armed forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMilitaryRoleIn
Context triple: [Commander-in-Chief, North Sea Fleet, isMilitaryRoleIn, United Kingdom armed forces]
  • A. isMilitaryOffice
    Indicates that an entity holds or is designated as a military office or official position within an armed forces structure.
  • B. isMilitaryOfficer
    Indicates that the subject holds an official position as an officer within a military organization.
  • C. isMilitaryStaffOf
    Indicates that one entity serves as military personnel working for, or assigned to, another entity (such as an organization, unit, or individual).
  • D. militaryRole chosen
    Indicates the specific function, position, or duty an entity holds within a military organization or context.
  • E. isMilitaryCommand
    Indicates that one entity holds formal military authority or command over another entity or group.
  • 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_69f224c28c1881908c33b45d689f1724 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6953bafb88190a860e9c68a3dd4b2 completed May 3, 2026, 12:22 a.m.
PD Predicate disambiguation batch_69f690ef92308190903a54fc74233269 completed May 3, 2026, 12:03 a.m.
Created at: April 29, 2026, 8:53 p.m.