Triple
T17519510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Schema |
E426648
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | JSON Schema Core |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: JSON Schema Core | Statement: [JSON Schema, hasComponent, JSON Schema Core]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JSON Schema Core Context triple: [JSON Schema, hasComponent, JSON Schema Core]
-
A.
JSON Schema (from 3.1.0)
chosen
JSON Schema (from 3.1.0) is a standardized vocabulary and specification for describing, validating, and documenting the structure and constraints of JSON data.
-
B.
JSON
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
-
C.
JSON5
JSON5 is an extension of the JSON data format that adds more human-friendly features like comments, trailing commas, and unquoted object keys while remaining largely compatible with standard JSON.
-
D.
JSON Working Group
The JSON Working Group is an IETF standards body responsible for developing and maintaining the formal specifications for the JSON data interchange format.
-
E.
Schematron
Schematron is a rule-based XML schema language that uses XPath expressions to define and validate complex structural and business constraints in XML documents.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
Created at: April 10, 2026, 5:49 a.m.