Triple

T27146693
Position Surface form Disambiguated ID Type / Status
Subject Mayoress of Arnhem E681968 entity
Predicate hasAlternativeRoleName P110696 FINISHED
Object spouse of the Mayor of Arnhem 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: spouse of the Mayor of Arnhem | Statement: [Mayoress of Arnhem, hasAlternativeRoleName, spouse of the Mayor of Arnhem]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternativeRoleName
Context triple: [Mayoress of Arnhem, hasAlternativeRoleName, spouse of the Mayor of Arnhem]
  • A. hasAlternativeFamilyName
    Indicates that an entity is associated with an additional or variant family name besides its primary family name.
  • B. hasAlternativeReferent
    Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
  • C. hasAlternativeProfile
    Indicates that an entity is associated with another profile that serves as an alternative or secondary representation of it.
  • D. haveAlternativeTitle chosen
    Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
  • E. hasTitleHolderAlternativeName
    Indicates that an entity serving as a title holder is known by an alternative or additional name.
  • 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_69eefacca3888190b67238d380e8f28b completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f67c9fe7b48190b79b4041357edb49 completed May 2, 2026, 10:37 p.m.
PD Predicate disambiguation batch_69f678cc272081909e5c70f1bc7407f0 completed May 2, 2026, 10:21 p.m.
Created at: April 27, 2026, 9:11 a.m.