Triple
T24623028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rules of Procedure of the General Assembly of States Parties to the World Heritage Convention |
E609464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | procedural document |
C6032
|
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: procedural document Context triple: [Rules of Procedure of the General Assembly of States Parties to the World Heritage Convention, instanceOf, procedural document]
-
A.
documentation preparation process
The documentation preparation process is the structured sequence of activities involved in planning, drafting, reviewing, revising, formatting, and finalizing documentation to ensure it is accurate, clear, and ready for distribution.
-
B.
governmental procedure
chosen
A governmental procedure is a formally established sequence of actions, rules, and decision-making steps that public authorities follow to create, implement, or enforce laws and policies.
-
C.
procedural law
Procedural law is the body of legal rules that governs the processes and methods by which courts and other legal authorities enforce rights, obligations, and justice in practice.
-
D.
PCT procedure document
A PCT procedure document is a formal record that outlines the standardized steps, requirements, and workflows for filing, processing, and managing international patent applications under the Patent Cooperation Treaty.
-
E.
design document
A design document is a detailed written plan that outlines the architecture, components, behavior, and rationale of a system or feature before implementation.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:32 a.m.