Triple
T9309525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO Memory of the World General Guidelines |
E223972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | official framework |
C4305
|
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: official framework Context triple: [UNESCO Memory of the World General Guidelines, instanceOf, official framework]
-
A.
official standard
chosen
An official standard is an authoritative, formally approved specification or guideline established by a recognized body to ensure consistency, compatibility, and quality across products, services, or processes.
-
B.
public institution framework
A public institution framework is a structured model that defines the principles, governance, processes, and accountability mechanisms guiding how public organizations operate and deliver services to society.
-
C.
official institution
An official institution is a formally established organization, typically created or sanctioned by a government or authoritative body, that exercises recognized powers and responsibilities within a defined legal or social framework.
-
D.
federal government framework
A federal government framework is a structural system that defines how power, responsibilities, and relationships are distributed and coordinated between a central authority and its constituent regional or state governments.
-
E.
software framework category
A software framework category is a conceptual grouping that classifies software frameworks based on shared characteristics such as purpose, architecture, technology stack, or domain of application.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.