Triple
T3535724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York Rite Craft Masonry |
E74765
|
entity |
| Predicate | ritualsInclude |
P29760
|
FINISHED |
| Object | obligations and charges to candidates |
—
|
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: obligations and charges to candidates | Statement: [York Rite Craft Masonry, ritualsInclude, obligations and charges to candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualsInclude Context triple: [York Rite Craft Masonry, ritualsInclude, obligations and charges to candidates]
-
A.
ritualCharacteristics
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
B.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
appearsInRitual
chosen
Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
-
D.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
E.
partOfRitual
Indicates that an action, object, or event is included as a component or step within a larger ritual.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcc4c1d081908938efb71938e1a3 |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.