Triple

T6618807
Position Surface form Disambiguated ID Type / Status
Subject Duchess of Saxony E149622 entity
Predicate traditionallyInvolvedIn P71548 FINISHED
Object court ceremonial 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: court ceremonial | Statement: [Duchess of Saxony, traditionallyInvolvedIn, court ceremonial]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallyInvolvedIn
Context triple: [Duchess of Saxony, traditionallyInvolvedIn, court ceremonial]
  • A. traditionallyKnownFor
    Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
  • B. traditionallyUsedBy
    Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
  • C. hasTraditionIn
    Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
  • D. traditionallyOneOf
    Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
  • E. traditionIncludes
    Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
  • 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_69c687ed8a9c81908bb671717cb192ef completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6bdb88cc881908f35648c15a7dc85 completed March 27, 2026, 5:26 p.m.
PD Predicate disambiguation batch_69c6ad007c1c8190af425f51011c7ad1 completed March 27, 2026, 4:14 p.m.
PDg Predicate description generation batch_69c6bdb76ec48190b59d576170970cc9 completed March 27, 2026, 5:26 p.m.
Created at: March 27, 2026, 1:58 p.m.