Triple

T397034
Position Surface form Disambiguated ID Type / Status
Subject Syriac Rite E9205 entity
Predicate hasCulturalRoot P1439 FINISHED
Object Syriac culture 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: Syriac culture | Statement: [Syriac Rite, hasCulturalRoot, Syriac culture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCulturalRoot
Context triple: [Syriac Rite, hasCulturalRoot, Syriac culture]
  • A. hasCulturalFeature
    Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
  • B. hasAssociatedCulture chosen
    Indicates that an entity is related to, influenced by, or characterized by a particular culture.
  • C. hasCulturalConcept
    Indicates that an entity embodies, includes, or is associated with a particular cultural idea, value, practice, or construct.
  • D. hasCulturalRole
    Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
  • E. hasCulturalSignificance
    Indicates that something holds notable meaning, value, or importance within a particular culture or cultural 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_69a2e8004cb88190b92ed1add6abf41a completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2ec8a941081909a152fda0ce24a98 completed Feb. 28, 2026, 1:24 p.m.
PD Predicate disambiguation batch_69a2e96d17d08190878d3a68b17d51ca completed Feb. 28, 2026, 1:11 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.