Triple
T10019837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakarta JSON Binding |
E200584
|
entity |
| Predicate | hasConcept |
P531
|
FINISHED |
| Object | Jsonb |
E200584
|
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: Jsonb | Statement: [Jakarta JSON Binding, hasConcept, Jsonb]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jsonb Context triple: [Jakarta JSON Binding, hasConcept, Jsonb]
-
A.
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.
-
B.
Jakarta JSON Binding
chosen
Jakarta JSON Binding is a Jakarta EE specification that defines a standard API for converting Java objects to and from JSON.
-
C.
BSON
BSON is a binary-encoded serialization format commonly used by MongoDB to store and transfer structured data efficiently while supporting additional data types beyond those in JSON.
-
D.
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.
-
E.
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.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd777b208190ad75eac79eec0c2f |
completed | April 2, 2026, 1:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d26aaa38188190aed8c18eccd8a79d |
completed | April 5, 2026, 1:59 p.m. |
Created at: March 30, 2026, 8:53 p.m.