Triple
T27640997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Council, 33° |
E696585
|
entity |
| Predicate | symbolicDegreeRequirement |
P163513
|
FINISHED |
| Object | Master Mason in good standing |
—
|
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: Master Mason in good standing | Statement: [Supreme Council, 33°, symbolicDegreeRequirement, Master Mason in good standing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicDegreeRequirement Context triple: [Supreme Council, 33°, symbolicDegreeRequirement, Master Mason in good standing]
-
A.
eligibleDegree
Indicates that an academic degree qualifies its holder to be considered eligible for a particular program, position, or requirement.
-
B.
hasDegree
Indicates that an entity possesses or has been awarded a specific academic or professional degree.
-
C.
possibleDegreeLevel
Indicates the academic or qualification level that an entity can potentially attain, offer, or be associated with.
-
D.
disciplinaryRequirement
Indicates that one entity imposes or specifies a disciplinary condition, rule, or obligation that another entity must satisfy.
-
E.
hasNumberOfDegrees
Indicates the quantity of academic degrees that an entity possesses.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 2:26 p.m.