Triple

T29761413
Position Surface form Disambiguated ID Type / Status
Subject Benjamin Caunt E753780 entity
Predicate hasAlternativeNamesakeRole P181147 FINISHED
Object possible eponym of Big Ben 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: possible eponym of Big Ben | Statement: [Benjamin Caunt, hasAlternativeNamesakeRole, possible eponym of Big Ben]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNamesakeRole
Context triple: [Benjamin Caunt, hasAlternativeNamesakeRole, possible eponym of Big Ben]
  • A. hasAlternativeToponymy
    Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
  • B. hasAlternativeFamilyName
    Indicates that an entity is associated with an additional or variant family name besides its primary family name.
  • C. hasNamesakeRoleFor
    Indicates that one entity holds a role or position that is named after, or serves as a namesake for, another entity.
  • D. knownAsBy
    Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
  • E. hasAlternativeNameForSameCity
    Indicates that one city name is an alternative or variant name referring to the same city as another name.
  • 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_69f0ef827ff88190ade56e0b0846b713 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f7626667f48190ad90867eb67ec582 completed May 3, 2026, 2:57 p.m.
PD Predicate disambiguation batch_69f76175d6608190b60b268e20f49ed9 completed May 3, 2026, 2:53 p.m.
PDg Predicate description generation batch_69f762651e088190baa21f25378a6065 completed May 3, 2026, 2:57 p.m.
Created at: April 28, 2026, 8:33 p.m.