Triple
T1640958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Deacon |
E35468
|
entity |
| Predicate | appearsInRitual |
P29760
|
FINISHED |
| Object | Masonic lodge opening ritual |
—
|
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: Masonic lodge opening ritual | Statement: [Junior Deacon, appearsInRitual, Masonic lodge opening ritual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInRitual Context triple: [Junior Deacon, appearsInRitual, Masonic lodge opening ritual]
-
A.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
B.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
C.
partOfRitual
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
D.
hasRitualSpace
Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
-
E.
hasRitualFocus
Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
- F. None of above. chosen
Provenance (4 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9192f975c8190bfd514a4b5a8786c |
completed | March 5, 2026, 5:48 a.m. |
Created at: March 4, 2026, 7:28 p.m.