Triple
T17519452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Schema |
E426648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | JSON vocabulary |
C1036
|
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: JSON vocabulary Context triple: [JSON Schema, instanceOf, JSON vocabulary]
-
A.
controlled vocabulary
chosen
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.
-
B.
JSON specification
A JSON specification defines the structured format, syntax rules, and data types for representing and exchanging data using JavaScript Object Notation.
-
C.
controlled vocabulary database
A controlled vocabulary database is a structured repository that stores standardized terms and their defined relationships to ensure consistent, precise description and retrieval of information across systems.
-
D.
lexical item
A lexical item is a single unit of meaning in a language, such as a word or fixed expression, that functions as an entry in the mental or written lexicon.
-
E.
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.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.