Triple

T16236182
Position Surface form Disambiguated ID Type / Status
Subject Ásmundur Grey-haired E394116 entity
Predicate familyNamePattern P122278 FINISHED
Object patronymic system (Ásmundarson for his son) 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: patronymic system (Ásmundarson for his son) | Statement: [Ásmundur Grey-haired, familyNamePattern, patronymic system (Ásmundarson for his son)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: familyNamePattern
Context triple: [Ásmundur Grey-haired, familyNamePattern, patronymic system (Ásmundarson for his son)]
  • A. familyNamePart
    Indicates that one string is a component or segment of a person's full family name.
  • B. familyName
    Indicates that one entity is the family (last) name associated with another entity (typically a person).
  • C. familyNameIn
    Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
  • D. familyNameDerivedFrom
    Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
  • E. laterFamilyNameForm
    Indicates that one family name is a later or subsequent form of another family name, reflecting a change or evolution over time.
  • 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_69d87f204df88190a8f88923decf9835 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2455abc608190ba3308c15c9e8a23 completed April 17, 2026, 2:36 p.m.
PD Predicate disambiguation batch_69e219ee6f6481909663b388dc99770a completed April 17, 2026, 11:30 a.m.
PDg Predicate description generation batch_69e21e55a2388190b29a045a8c608ba4 completed April 17, 2026, 11:49 a.m.
Created at: April 10, 2026, 5:04 a.m.