Triple
T1869640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON |
E39004
|
entity |
| Predicate | fullName |
P16
|
FINISHED |
| Object | JavaScript Object Notation |
E39004
|
NE FINISHED |
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: JavaScript Object Notation | Statement: [JSON, fullName, JavaScript Object Notation]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JavaScript Object Notation Context triple: [JSON, fullName, JavaScript Object Notation]
-
A.
JSON
chosen
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
-
B.
Jakarta JSON Processing
Jakarta JSON Processing is a Jakarta EE specification that defines a standard API for parsing, generating, transforming, and querying JSON data in Java applications.
-
C.
Jakarta JSON Binding
Jakarta JSON Binding is a Jakarta EE specification that defines a standard API for converting Java objects to and from JSON.
-
D.
JSON-LD
JSON-LD is a JSON-based format for encoding Linked Data, enabling structured data to be easily shared and understood across the web.
-
E.
JSON Web Tokens (JWT)
JSON Web Tokens (JWT) are a compact, URL-safe standard for securely transmitting digitally signed claims between parties, commonly used for stateless authentication and authorization in web applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0b95c0c8190a37907755541f8c6 |
completed | March 7, 2026, 4:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69add1dab2a481909adb0a3132348cee |
completed | March 8, 2026, 7:45 p.m. |
Created at: March 4, 2026, 7:34 p.m.