Triple
T4278143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON API |
E97089
|
entity |
| Predicate | fullName |
P16
|
FINISHED |
| Object | JSON:API |
E97089
|
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: JSON:API | Statement: [JSON API, fullName, JSON:API]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JSON:API Context triple: [JSON API, fullName, JSON:API]
-
A.
JSON API
chosen
JSON API is a standardized specification for building JSON-based RESTful APIs that defines how clients should request and modify resources in a consistent, structured format.
-
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.
Restout
Restout is a French surname associated with a notable family of painters active from the 17th to 18th centuries.
-
D.
REST API
A REST API is a web service interface that allows clients to interact with resources over HTTP using standard methods like GET, POST, PUT, and DELETE in a stateless, structured way.
-
E.
OpenAPI
OpenAPI is a widely adopted, language-agnostic specification for describing and documenting RESTful APIs in a standardized, machine-readable format.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350201ac88190b9d8980da5f0d03d |
completed | March 12, 2026, 11:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5b7b708b481908c1683741f84ee55 |
completed | March 14, 2026, 7:32 p.m. |
Created at: March 12, 2026, 11:07 p.m.