Triple
T7934241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenID Connect |
E184249
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object | JSON Web Token |
E192655
|
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 Web Token | Statement: [OpenID Connect, relatedStandard, JSON Web Token]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JSON Web Token Context triple: [OpenID Connect, relatedStandard, JSON Web Token]
-
A.
JSON Web Tokens (JWT)
chosen
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.
-
B.
JWT
JWT is a historic global advertising agency, originally known as J. Walter Thompson, recognized as one of the pioneers of modern marketing and brand communications.
-
C.
JSON Web Encryption
JSON Web Encryption (JWE) is a standard for securely encrypting arbitrary data as JSON-based tokens, commonly used in modern web security protocols and identity frameworks.
-
D.
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.
-
E.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aeb132c8190bea4906aaf51b869 |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe019a094819082baecdcb007c84f |
completed | March 31, 2026, 2:54 p.m. |
Created at: March 30, 2026, 5:08 p.m.