Triple

T13824929
Position Surface form Disambiguated ID Type / Status
Subject irregular Freemasonry E332225 entity
Predicate mayDifferFromRegularFreemasonryIn P53790 FINISHED
Object membership requirements 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: membership requirements | Statement: [irregular Freemasonry, mayDifferFromRegularFreemasonryIn, membership requirements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayDifferFromRegularFreemasonryIn
Context triple: [irregular Freemasonry, mayDifferFromRegularFreemasonryIn, membership requirements]
  • A. hasMasonicContext
    Indicates that something is related to, influenced by, or situated within the traditions, symbolism, practices, or institutions of Freemasonry.
  • B. hasMasonicBodyType
    Indicates that an entity is associated with, or classified according to, a specific type or category of Masonic body.
  • C. isCeremoniallyDistinctFrom
    Indicates that two entities are formally separated or differentiated from each other within a ritual, ceremonial, or symbolic context.
  • D. mayDifferFrom chosen
    Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
  • E. ritualSecrecy
    Indicates that certain aspects of a ritual are intentionally concealed or restricted from outsiders or non-initiated participants.
  • 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_69d81c5ae7c88190b0dd41bdafeb5999 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0285fb7c8190be4b90bdc0d6fa53 completed April 14, 2026, 9:01 a.m.
PD Predicate disambiguation batch_69dbc86668e08190ba9135d1c3f38d35 completed April 12, 2026, 4:29 p.m.
Created at: April 9, 2026, 10:13 p.m.