Triple
T10019900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakarta Annotations |
E200586
|
entity |
| Predicate | containsAnnotation |
P4981
|
FINISHED |
| Object |
jakarta.annotation.PostConstruct
jakarta.annotation.PostConstruct is a lifecycle callback annotation used in Jakarta-based applications to mark a method that should be executed after dependency injection and initialization are complete.
|
E200586
|
NE FINISHED |
How this triple was built (5 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: jakarta.annotation.PostConstruct | Statement: [Jakarta Annotations, containsAnnotation, jakarta.annotation.PostConstruct]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: jakarta.annotation.PostConstruct Context triple: [Jakarta Annotations, containsAnnotation, jakarta.annotation.PostConstruct]
-
A.
Jakarta Annotations
Jakarta Annotations is a Jakarta EE specification that defines a set of standard Java annotations used to simplify configuration and behavior in enterprise applications.
-
B.
Jakarta Bean Validation
Jakarta Bean Validation is a Jakarta EE specification that defines a standard, annotation-based way to declare and enforce constraints on Java object models, typically used for validating user input and application data.
-
C.
Jakarta Persistence
Jakarta Persistence is a Jakarta EE specification that defines a standard API for managing relational data persistence in Java applications using object-relational mapping (ORM).
-
D.
Jakarta Enterprise Beans
Jakarta Enterprise Beans is a Jakarta EE server-side component architecture that simplifies the development of transactional, secure, and scalable business logic in Java enterprise applications.
-
E.
Jakarta EE
Jakarta EE is a set of specifications that extend the Java SE platform for enterprise-level applications, defining standard APIs for building scalable, secure, and portable Java-based enterprise software.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: jakarta.annotation.PostConstruct Triple: [Jakarta Annotations, containsAnnotation, jakarta.annotation.PostConstruct]
Generated description
jakarta.annotation.PostConstruct is a lifecycle callback annotation used in Jakarta-based applications to mark a method that should be executed after dependency injection and initialization are complete.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: jakarta.annotation.PostConstruct Target entity description: jakarta.annotation.PostConstruct is a lifecycle callback annotation used in Jakarta-based applications to mark a method that should be executed after dependency injection and initialization are complete.
-
A.
Jakarta Annotations
chosen
Jakarta Annotations is a Jakarta EE specification that defines a set of standard Java annotations used to simplify configuration and behavior in enterprise applications.
-
B.
Jakarta Bean Validation
Jakarta Bean Validation is a Jakarta EE specification that defines a standard, annotation-based way to declare and enforce constraints on Java object models, typically used for validating user input and application data.
-
C.
Jakarta Persistence
Jakarta Persistence is a Jakarta EE specification that defines a standard API for managing relational data persistence in Java applications using object-relational mapping (ORM).
-
D.
Jakarta Enterprise Beans
Jakarta Enterprise Beans is a Jakarta EE server-side component architecture that simplifies the development of transactional, secure, and scalable business logic in Java enterprise applications.
-
E.
Jakarta EE
Jakarta EE is a set of specifications that extend the Java SE platform for enterprise-level applications, defining standard APIs for building scalable, secure, and portable Java-based enterprise software.
- F. None of above.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAnnotation Context triple: [Jakarta Annotations, containsAnnotation, jakarta.annotation.PostConstruct]
-
A.
typeOfAnnotation
chosen
Indicates that one entity is an annotation and specifies the kind or category of that annotation in relation to the annotated item.
-
B.
hasContainmentType
Indicates the specific way in which one entity is contained within or enclosed by another.
-
C.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
D.
containsDeclaration
Indicates that one entity includes or holds within it a formal declaration associated with another entity.
-
E.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
- F. None of above.
Provenance (6 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. |
| NEDg | Description generation | batch_69d26b84271881909c3a1b8a05e2c8a2 |
completed | April 5, 2026, 2:02 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d26f50dc008190866f0ba45b671560 |
completed | April 5, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.