Triple

T23301279
Position Surface form Disambiguated ID Type / Status
Subject Reginar E590308 entity
Predicate hasEtymologicalFamily P42488 FINISHED
Object Germanic 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: Germanic personal names | Statement: [Reginar, hasEtymologicalFamily, Germanic personal names]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEtymologicalFamily
Context triple: [Reginar, hasEtymologicalFamily, Germanic personal names]
  • A. etymologicalLanguageFamily chosen
    Indicates that one entity is the language family from which the other entity is etymologically derived or historically originates.
  • B. hasEtymologicalBasis
    Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
  • C. sharesLinguisticFamilyWith
    Indicates that two languages belong to the same linguistic family or branch within a language family.
  • D. hasEtymologyConcept
    Indicates that something derives its origin, form, or meaning from a particular etymological concept or source.
  • E. languageFamilyRelation
    Indicates a relationship where one language belongs to, descends from, or is otherwise classified within a particular language family.
  • 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_69e25d1c0ecc8190a355aa229f06d0e0 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196d37fd08190ad2d199c54324c02 completed April 29, 2026, 5:27 a.m.
PD Predicate disambiguation batch_69effcf325f88190b320268c3c551abb completed April 28, 2026, 12:18 a.m.
Created at: April 17, 2026, 5:04 p.m.