Triple
T1390308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDFS |
E29939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RDF vocabulary |
C2888
|
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: RDF vocabulary Context triple: [RDFS, instanceOf, RDF vocabulary]
-
A.
Web ontology language
A web ontology language is a formal language designed for representing rich, machine-interpretable knowledge about concepts, relationships, and constraints on the web to enable automated reasoning and interoperability.
-
B.
controlled vocabulary
A controlled vocabulary is a standardized, curated set of terms and phrases used consistently to describe and organize information, ensuring uniformity and improving search and retrieval.
-
C.
bibliographic authority data set
A bibliographic authority data set is a structured collection of standardized records that uniquely identify and describe entities (such as persons, organizations, works, and subjects) used to control and link names and headings in bibliographic and library catalogs.
-
D.
Knowledge representation language
chosen
A knowledge representation language is a formal system used to encode information about the world in a structured, machine-interpretable way so that computers can reason about it.
-
E.
ontology
An ontology is a structured conceptual model that defines the entities, relationships, and rules within a specific domain to enable shared understanding and reasoning.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.