Triple
T27888675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HiveServer2 |
E705293
|
entity |
| Predicate | supportsAuthorizationModel |
P19966
|
FINISHED |
| Object | SQL standard based authorization |
—
|
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: SQL standard based authorization | Statement: [HiveServer2, supportsAuthorizationModel, SQL standard based authorization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAuthorizationModel Context triple: [HiveServer2, supportsAuthorizationModel, SQL standard based authorization]
-
A.
supportsAccessModel
Indicates that one entity enables, permits, or is compatible with a particular access model used by another entity.
-
B.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
C.
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.
-
D.
supportsRoleBasedAccessControl
Indicates that an entity provides or enables role-based access control, allowing permissions or access rights to be managed based on assigned roles.
-
E.
supportsModelType
chosen
Indicates that an entity is compatible with, or can operate using, a specified model type.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: April 27, 2026, 6:34 p.m.