Triple

T31382131
Position Surface form Disambiguated ID Type / Status
Subject Paul Godfrey E800489 entity
Predicate militaryBranchOfCommand P91149 FINISHED
Object Royal Air Force 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: Royal Air Force | Statement: [Paul Godfrey, militaryBranchOfCommand, Royal Air Force]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryBranchOfCommand
Context triple: [Paul Godfrey, militaryBranchOfCommand, Royal Air Force]
  • A. militaryBranchDomain
    Indicates that one entity serves as the military branch or armed forces component associated with the domain, jurisdiction, or organizational scope of another entity.
  • B. militaryBranchComponentOf
    Indicates that one military branch or unit is an organizational component or subordinate part of a larger military branch or force.
  • C. militaryBranchAssociatedWith chosen
    Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
  • D. militaryBranchOfGovernment
    Indicates that a military organization functions as an official branch or component of a government.
  • 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_69f224e84da08190abfc2f17494a33c8 completed April 29, 2026, 3:34 p.m.
NER Named-entity recognition batch_69f7764ab1fc81909f9348db87bd7692 completed May 3, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69f76905d9c88190b1ee810bc9ab644f completed May 3, 2026, 3:25 p.m.
Created at: April 29, 2026, 9:19 p.m.