Triple

T30407
Position Surface form Disambiguated ID Type / Status
Subject Jews E607 entity
Predicate hasCulturalIdentity P1439 FINISHED
Object Jewish 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: Jewish culture | Statement: [Jews, hasCulturalIdentity, Jewish culture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCulturalIdentity
Context triple: [Jews, hasCulturalIdentity, Jewish culture]
  • A. hasAssociatedCulture chosen
    Indicates that an entity is related to, influenced by, or characterized by a particular culture.
  • B. hasCulturalSignificance
    Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
  • C. hasCulturalSignificanceFor
    Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
  • D. ethnicOrigin
    Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
  • E. hasHeritage
    Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
  • 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_69a2479dec388190967ba648663442c9 completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a2490d80a0819083bf604c1229e903 completed Feb. 28, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69a2486eb01881909241540dda28e1ff completed Feb. 28, 2026, 1:44 a.m.
Created at: Feb. 28, 2026, 1:44 a.m.