Triple
T17561064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoServer |
E427695
|
entity |
| Predicate | supportsAuthorization |
P60443
|
FINISHED |
| Object | role-based access control |
—
|
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: role-based access control | Statement: [GeoServer, supportsAuthorization, role-based access control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAuthorization Context triple: [GeoServer, supportsAuthorization, role-based access control]
-
A.
canAuthorize
Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
-
B.
supportsLicense
Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
-
C.
authorizedIn
Indicates that an entity has been granted official permission or legal authority to act, operate, or be valid within a specified context, domain, or jurisdiction.
-
D.
usedToAuthorize
chosen
Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an action.
-
E.
supportsACLs
Indicates that one entity provides or is compatible with access control lists (ACLs) for managing permissions on another entity.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.