Triple
T32924688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | messages of the Universal House of Justice |
E842234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authoritative guidance documents |
C989
|
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: authoritative guidance documents Context triple: [messages of the Universal House of Justice, instanceOf, authoritative guidance documents]
-
A.
advisory document series
An advisory document series is a recurring collection of written guidance materials that provide expert recommendations, best practices, and updates on a specific topic or domain over time.
-
B.
architectural guidance document series
A curated, structured collection of documents that provide consistent principles, patterns, and recommendations to guide architectural decisions across related projects or domains.
-
C.
normative guideline
chosen
A normative guideline is a prescriptive rule or principle that defines how things ought to be done or how people ought to behave within a particular context or system.
-
D.
regulatory document
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.
-
E.
U.S. GAAP authoritative guidance
U.S. GAAP authoritative guidance is the officially recognized set of accounting standards, rules, and interpretations issued by designated standard-setting bodies (primarily the FASB and SEC) that entities must follow when preparing financial statements in the United States.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.