Triple
T19435574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JCache (JSR-107) |
E486217
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | JSR-107 |
—
|
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: JSR-107 | Statement: [JCache (JSR-107), alsoKnownAs, JSR-107]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JSR-107 Context triple: [JCache (JSR-107), alsoKnownAs, JSR-107]
-
A.
JCache (JSR-107)
chosen
JCache (JSR-107) is the standard Java API specification for in-memory caching, defining a common, vendor-neutral way to create, access, and manage caches in Java applications.
-
B.
JSR 317
JSR 317 is the Java Community Process specification that standardizes the Java Persistence API (JPA) for object-relational mapping and data persistence in Java applications.
-
C.
JSR 338
JSR 338 is the Java Community Process specification that defines version 2.1 of the Java Persistence API (JPA) for object-relational mapping in Java.
-
D.
JSR 352
JSR 352 is the original Java batch processing specification that defined a standardized model for batch applications on the Java platform.
-
E.
PSR-17
PSR-17 is a PHP standard that defines interfaces for HTTP message factories, enabling consistent creation of requests, responses, and related HTTP objects across frameworks and libraries.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6336001488190a05f372779711ed2 |
completed | April 20, 2026, 2:08 p.m. |
Created at: April 10, 2026, 1:37 p.m.