Triple

T35313313
Position Surface form Disambiguated ID Type / Status
Subject Welchman E1019836 entity
Predicate hasNotableAssociationThroughBearer GENERATED
Object British codebreaking UNRECOGNIZED GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableAssociationThroughBearer
Context triple: [Welchman, hasNotableAssociationThroughBearer, British codebreaking]
  • A. hasNotableBearer
    Indicates that an entity (such as a name, title, or identifier) is borne by at least one notable person or entity.
  • B. hasNotableBearerConcept
    Indicates that a concept is notably associated with or exemplified by a particular bearer (such as a person, group, or entity).
  • C. hasNotableBearerFamilyConnection
    Indicates a relationship where one entity has a notable bearer who is connected to another entity through a family or kinship tie.
  • D. hasNotableSingleBearer
    Indicates that the relationship holds when a name, title, or identifier is notably associated with exactly one specific bearer, rather than shared among many.
  • E. hasNotableFieldOfBearers
    Indicates that the entities share a significant or distinguished area of activity, expertise, or achievement associated with their bearers.
  • F. None of above. chosen

Provenance (1 batch)

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_69f76de9d45c81908a2ed0956b448b65 completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:03 p.m.