Triple

T18303218
Position Surface form Disambiguated ID Type / Status
Subject Anson E438409 entity
Predicate hasNameDayInformation P131263 FINISHED
Object not widely associated with a specific name day 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: not widely associated with a specific name day | Statement: [Anson, hasNameDayInformation, not widely associated with a specific name day]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNameDayInformation
Context triple: [Anson, hasNameDayInformation, not widely associated with a specific name day]
  • A. hasNameDay
    Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
  • B. hasNameDayRelation
    Indicates a relationship where a person’s name is associated with a specific name day or feast day in a calendar.
  • C. hasNameDayContext
    Indicates that an entity’s name day is interpreted or celebrated within a specific contextual framework (such as culture, calendar system, or tradition).
  • D. hasNameDayBaseName
    Indicates that an entity’s name day is based on or associated with a particular base name.
  • E. hasNameDayOrReligiousUsage
    Indicates that an entity has an associated name day celebration or is used in a religious or liturgical context.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5018176d481909536f50689f878d2 completed April 19, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69e44fdf43d08190bbcfb6b1fe3cc0ee completed April 19, 2026, 3:45 a.m.
PDg Predicate description generation batch_69e451a0ba208190a5fe92832a8f7a49 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 10:35 a.m.