Triple

T30896848
Position Surface form Disambiguated ID Type / Status
Subject Safavid royal court E787042 entity
Predicate courtCultureFeature P15786 FINISHED
Object elaborate etiquette 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: elaborate etiquette | Statement: [Safavid royal court, courtCultureFeature, elaborate etiquette]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: courtCultureFeature
Context triple: [Safavid royal court, courtCultureFeature, elaborate etiquette]
  • A. courtCulture chosen
    Indicates the prevailing norms, practices, and behavioral expectations that characterize how a particular court operates and conducts its proceedings.
  • B. courtFeatured
    Indicates that a particular court prominently presented, highlighted, or showcased a given entity (such as a case, event, or person) in an official or notable context.
  • C. courtSphere
    Indicates a relationship where one entity operates within, is associated with, or has authority in a particular judicial or legal domain or sphere.
  • D. courtStyle
    Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
  • E. courtContext
    Indicates the legal or judicial setting, circumstances, or framework within which a court-related action or relationship takes place.
  • 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_69f224bcbcb48190836df847424e4057 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6a916d2e08190bafc01cba73b6469 completed May 3, 2026, 1:47 a.m.
PD Predicate disambiguation batch_69f6a7548eb48190a69b60a3c6ad53b9 completed May 3, 2026, 1:39 a.m.
Created at: April 29, 2026, 8:49 p.m.