Triple
T4524343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Complementary Norms of the Society of Jesus |
E103341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal regulatory document |
C12268
|
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: internal regulatory document Context triple: [Complementary Norms of the Society of Jesus, instanceOf, internal regulatory document]
-
A.
regulatory document
chosen
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
-
B.
internal administrative body
An internal administrative body is an organized group within an institution responsible for managing, coordinating, and overseeing its internal operations, policies, and support functions.
-
C.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
D.
regulatory filing
A regulatory filing is an official document or set of documents submitted to a government or regulatory authority to report required information, demonstrate compliance, or request approval related to an organization’s activities.
-
E.
international diplomatic document
An international diplomatic document is a formal written instrument exchanged between states or international organizations to record, communicate, or formalize agreements, positions, or understandings in the conduct of foreign relations.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:03 p.m.