Triple

T24118606
Position Surface form Disambiguated ID Type / Status
Subject Stolin Hasidism E597587 entity
Predicate hasDynasticLine P13166 FINISHED
Object Karlin-Stolin Rebbe lineage 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: Karlin-Stolin Rebbe lineage | Statement: [Stolin Hasidism, hasDynasticLine, Karlin-Stolin Rebbe lineage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDynasticLine
Context triple: [Stolin Hasidism, hasDynasticLine, Karlin-Stolin Rebbe lineage]
  • A. hasDynasticConnections
    Indicates that one entity is related to another through familial or hereditary ties between ruling or noble dynasties.
  • B. dynasticBranch chosen
    Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
  • C. isDynastic
    Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
  • D. dynasticInheritance
    Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
  • E. dynasticLegacy
    Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
  • 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_69e288c74200819098ab875b592cb39f completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dee091c48190a55d36f28c332749 completed April 29, 2026, 10:35 a.m.
PD Predicate disambiguation batch_69f1765650fc8190a6bc1eb512b240bf completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11:05 p.m.