Triple
T32709667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | jakarta.annotation.security.RolesAllowed |
E836363
|
entity |
| Predicate | canBeAppliedOn |
P1129
|
FINISHED |
| Object | Jakarta RESTful Web Services resource methods |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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 RESTful Web Services resource methods | Statement: [jakarta.annotation.security.RolesAllowed, canBeAppliedOn, Jakarta RESTful Web Services resource methods]
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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe604db4d48190a8e2176452f50e58 |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 1, 2026, 1:10 a.m.