Triple

T9276054
Position Surface form Disambiguated ID Type / Status
Subject Toomas E222950 entity
Predicate hasNameDayInEstonia P59993 FINISHED
Object December 21 — 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: December 21 | Statement: [Toomas, hasNameDayInEstonia, December 21]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNameDayInEstonia
Context triple: [Toomas, hasNameDayInEstonia, December 21]
  • A. hasNameInEstonian
    Indicates that an entity is associated with a specific name expressed in the Estonian language.
  • B. hasNameDay
    Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
  • C. hasNameDayRelation chosen
    Indicates a relationship where a person’s name is associated with a specific name day or feast day in a calendar.
  • D. nameDayDateInSweden
    Indicates the specific calendar date in Sweden on which a given person’s name day is celebrated.
  • 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.

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_69ca841ffe208190aa7bcffbef2f8379 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd07c71b5c8190b5b7b5ab4224e9d3 completed April 1, 2026, 11:55 a.m.
PD Predicate disambiguation batch_69cc7a537bbc8190baee71f556e52a7b completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:34 p.m.