Triple
T13770625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men of the Great Assembly |
E330870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary religious body |
C16143
|
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: legendary religious body Context triple: [Men of the Great Assembly, instanceOf, legendary religious body]
-
A.
historical religious institution
chosen
A historical religious institution is an organized body or establishment that has played a significant role in shaping and preserving religious beliefs, practices, and cultural traditions over an extended period in history.
-
B.
former religious organization
A former religious organization is a once-active group formally dedicated to shared religious beliefs and practices that has since disbanded, dissolved, or otherwise ceased to function as an organized entity.
-
C.
organ of an international religious organization
An organ of an international religious organization is a formally established body or office within the organization that carries out specific governance, administrative, doctrinal, or representative functions on its behalf at the global level.
-
D.
denominational body
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
E.
religious-military order
A religious-military order is an organized group that combines a shared religious or spiritual mission with a structured, often hierarchical, military function or code of conduct.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:10 p.m.