Triple
T28125507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Rite |
E710914
|
entity |
| Predicate | usesRitualLanguage |
P124620
|
FINISHED |
| Object | allegory |
—
|
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: allegory | Statement: [Scottish Rite, usesRitualLanguage, allegory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRitualLanguage Context triple: [Scottish Rite, usesRitualLanguage, allegory]
-
A.
languageUsedInRituals
Indicates that a particular language is employed as the medium of speech, chant, or recitation during specific rituals or ceremonial practices.
-
B.
usesRitually
chosen
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
C.
languageOfIncantation
Indicates that a specified language is the one in which a particular incantation is spoken or written.
-
D.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
E.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 9:19 p.m.