Triple
T10019291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakarta Expression Language |
E200573
|
entity |
| Predicate | scopeAccess |
P42519
|
FINISHED |
| Object | request scope |
—
|
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: request scope | Statement: [Jakarta Expression Language, scopeAccess, request scope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeAccess Context triple: [Jakarta Expression Language, scopeAccess, request scope]
-
A.
accessScope
chosen
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
B.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
scopeClaim
Indicates that a claim or statement applies within a specified scope, context, or boundary.
-
E.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
- F. None of above.
Provenance (3 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_69cdcd4f3a988190892cc698109be8b8 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.