Triple
T19586852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java EE 5 |
E490126
|
entity |
| Predicate | includesSpecification |
P19701
|
FINISHED |
| Object | Java Authorization Contract for Containers 1.1 |
—
|
NE NERFINISHED |
How this triple was built (3 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: Java Authorization Contract for Containers 1.1 | Statement: [Java EE 5, includesSpecification, Java Authorization Contract for Containers 1.1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Java Authorization Contract for Containers 1.1 Context triple: [Java EE 5, includesSpecification, Java Authorization Contract for Containers 1.1]
-
A.
Java Authentication Service Provider Interface for Containers (JASPIC)
Java Authentication Service Provider Interface for Containers (JASPIC) is a pluggable Java EE security framework that standardizes how authentication modules integrate with application servers and web containers.
-
B.
Binary Authorization
Binary Authorization is a Google Cloud security service that enforces deploy-time image verification and policy controls to ensure only trusted container images are run in your environments.
-
C.
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.
-
D.
JSR 316
JSR 316 is the Java Community Process specification that defines the Java Platform, Enterprise Edition 6 (Java EE 6), outlining its APIs, architecture, and component model for enterprise applications.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Java Authorization Contract for Containers 1.1 Target entity description: Java Authorization Contract for Containers 1.1 is a Java EE security specification that defines a pluggable, policy-based authorization framework for controlling access to resources within Java application server containers.
-
A.
Java Authentication Service Provider Interface for Containers (JASPIC)
Java Authentication Service Provider Interface for Containers (JASPIC) is a pluggable Java EE security framework that standardizes how authentication modules integrate with application servers and web containers.
-
B.
Binary Authorization
Binary Authorization is a Google Cloud security service that enforces deploy-time image verification and policy controls to ensure only trusted container images are run in your environments.
-
C.
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.
-
D.
JSR 316
JSR 316 is the Java Community Process specification that defines the Java Platform, Enterprise Edition 6 (Java EE 6), outlining its APIs, architecture, and component model for enterprise applications.
-
E.
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.
- F. None of above. chosen
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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640523d10819091320a61456f6437 |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.