Triple
T9170268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Comment No. 1 on the implementation of article 3 of the Convention |
E220063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authoritative interpretative 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: authoritative interpretative document Context triple: [General Comment No. 1 on the implementation of article 3 of the Convention, instanceOf, authoritative interpretative 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.
reference document
A reference document is an organized, authoritative source of information designed to be consulted as needed for specific facts, standards, or procedures rather than read sequentially.
-
C.
magisterial document
A magisterial document is an official teaching text issued by the authority of the Church’s magisterium to articulate, clarify, or develop doctrine and moral guidance for the faithful.
-
D.
constitutional interpreter
A constitutional interpreter is an entity—such as a judge, scholar, or institution—that analyzes and applies the text, structure, history, and principles of a constitution to resolve legal and political questions.
-
E.
founding document
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:22 p.m.