Triple
T11656383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Authentication |
E277020
|
entity |
| Predicate | loginInformationStoredIn |
P91403
|
FINISHED |
| Object | sys.sql_logins |
—
|
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: sys.sql_logins | Statement: [SQL Server Authentication, loginInformationStoredIn, sys.sql_logins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loginInformationStoredIn Context triple: [SQL Server Authentication, loginInformationStoredIn, sys.sql_logins]
-
A.
loginOptions
Indicates the available methods or configurations a user can choose from when signing into a system or application.
-
B.
storesPasswordAs
chosen
Indicates that one entity keeps or maintains another entity’s password in a particular form or location.
-
C.
loginScope
Indicates the specific permissions, access range, or contextual boundaries under which a user or system is authenticated during a login session.
-
D.
anonymousLoginUsername
Indicates that a username is used specifically for logging in anonymously, without revealing the user's real identity.
-
E.
authenticationRequired
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.