Triple

T15889081
Position Surface form Disambiguated ID Type / Status
Subject Wiebe E385267 entity
Predicate isRelatedNameInOnomastics P3889 FINISHED
Object Frisian personal names 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: Frisian personal names | Statement: [Wiebe, isRelatedNameInOnomastics, Frisian personal names]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRelatedNameInOnomastics
Context triple: [Wiebe, isRelatedNameInOnomastics, Frisian personal names]
  • A. isRelatedName chosen
    Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
  • B. isPatronymicOrToponymic
    Indicates that a name or term is derived either from a person's name (patronymic) or from a place name (toponymic).
  • C. isMatronymicOf
    Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
  • D. hasNameMeaningRelation
    Indicates that there is a relationship between an entity and a name that conveys or encodes a particular meaning or significance.
  • E. isPraenomenOf
    Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e174de2cd48190ab18e48c9f051a2a completed April 16, 2026, 11:46 p.m.
PD Predicate disambiguation batch_69e142c3e18c8190bb7b023f4a0eaebb completed April 16, 2026, 8:12 p.m.
Created at: April 10, 2026, 4:51 a.m.