Triple
T32709699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | jakarta.annotation.security.DeclareRoles |
E836364
|
entity |
| Predicate | valueElementType |
P176065
|
FINISHED |
| Object | String array of role names |
—
|
LITERAL 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: String array of role names | Statement: [jakarta.annotation.security.DeclareRoles, valueElementType, String array of role names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueElementType Context triple: [jakarta.annotation.security.DeclareRoles, valueElementType, String array of role names]
-
A.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
B.
fieldType
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
C.
codecsElementType
Indicates the specific type or category of an element within a codec or encoding structure.
-
D.
logicElementType
Indicates that one entity is classified as a specific type or category of logical element in relation to another.
-
E.
codeElementType
Indicates the specific kind or category of a code element (such as class, method, variable, etc.) within a codebase.
- F. None of above. chosen
Provenance (4 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:10 a.m.