Triple
T13825319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada (Francophone lodges) |
E332234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Francophone Masonic lodges |
C12127
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Francophone Masonic lodges Context triple: [Canada (Francophone lodges), instanceOf, Francophone Masonic lodges]
-
A.
Francophone organization
chosen
A Francophone organization is an entity whose primary activities, communication, and cultural orientation are conducted in French and focused on serving or representing French-speaking individuals or communities.
-
B.
French learned society
A French learned society is an organized association in France dedicated to advancing, preserving, and disseminating specialized knowledge in academic, scientific, or cultural fields.
-
C.
Masonic organization
A Masonic organization is a fraternal society structured around lodges and degrees that promotes moral development, mutual support, and charitable works through rituals, symbolism, and shared philosophical principles.
-
D.
Breton-language organization
A Breton-language organization is an entity dedicated to promoting, preserving, and using the Breton language through cultural, educational, social, or advocacy activities.
-
E.
organ of the Organisation internationale de la Francophonie
An organ of the Organisation internationale de la Francophonie is an institutional body established within the OIF that carries out specific functions such as decision-making, coordination, implementation, or consultation in support of the Francophone community’s objectives.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 9, 2026, 10:13 p.m.