Triple
T13916204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Orient of Belgium |
E334626
|
entity |
| Predicate | masonicCurrent |
P50336
|
FINISHED |
| Object | liberal Freemasonry |
—
|
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: liberal Freemasonry | Statement: [Grand Orient of Belgium, masonicCurrent, liberal Freemasonry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: masonicCurrent Context triple: [Grand Orient of Belgium, masonicCurrent, liberal Freemasonry]
-
A.
hasMasonicContext
Indicates that something is related to, influenced by, or situated within the traditions, symbolism, practices, or institutions of Freemasonry.
-
B.
masonicObedienceType
Indicates the specific organizational or jurisdictional form of authority under which a Masonic body operates.
-
C.
currentMSP
Indicates that an entity is the managed service provider (MSP) that is currently active or in effect for another entity.
-
D.
hasMasonicBodyType
chosen
Indicates that an entity is associated with, or classified according to, a specific type or category of Masonic body.
-
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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.