Triple
T31059615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford Single Sign-On |
E791493
|
entity |
| Predicate | loginCredentialType |
P6396
|
FINISHED |
| Object | Oxford Single Sign-On username |
—
|
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: Oxford Single Sign-On username | Statement: [Oxford Single Sign-On, loginCredentialType, Oxford Single Sign-On username]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loginCredentialType Context triple: [Oxford Single Sign-On, loginCredentialType, Oxford Single Sign-On username]
-
A.
credentialType
chosen
Indicates the specific kind or category of credential associated with an entity or relationship.
-
B.
authenticationType
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
-
C.
logonType
Indicates the manner or method by which a user or entity authenticates and establishes a login session.
-
D.
loginOptions
Indicates the available methods or configurations a user can choose from when signing into a system or application.
-
E.
loginScope
Indicates the specific permissions, access range, or contextual boundaries under which a user or system is authenticated during a login session.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69575e1948190b242d53f918f172a |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9 p.m.