Triple
T1919740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SKOS |
E40098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | knowledge organization system model |
C6938
|
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: knowledge organization system model Context triple: [SKOS, instanceOf, knowledge organization system model]
-
A.
open knowledge organization
An open knowledge organization is a collaborative, transparent system for structuring, connecting, and sharing information that allows broad participation in creating, maintaining, and reusing knowledge resources.
-
B.
knowledge representation framework
A knowledge representation framework is a structured system of formalisms, models, and conventions used to encode, organize, and manipulate information so that it can be interpreted and reasoned about by humans and machines.
-
C.
bibliographic data model
chosen
A bibliographic data model is a structured framework that defines how information about published and unpublished resources (such as books, articles, and digital media) is represented, organized, and related for purposes of description, discovery, and management.
-
D.
open knowledge program
An open knowledge program is an initiative designed to create, share, and maintain freely accessible, collaboratively developed information resources for public use and learning.
-
E.
scientific model collection
A scientific model collection is an organized set of related theoretical, computational, or empirical models curated to represent, compare, and analyze phenomena within a specific scientific domain.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.