Triple
T19585467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty ID-FF |
E490095
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | SAML |
E345752
|
NE 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: SAML | Statement: [Liberty ID-FF, relatedTo, SAML]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAML Context triple: [Liberty ID-FF, relatedTo, SAML]
-
A.
SAML
chosen
SAML (Security Assertion Markup Language) is an XML-based open standard for exchanging authentication and authorization data between identity providers and service providers, commonly used for single sign-on (SSO) in web applications.
-
B.
SSO
SSO is the abbreviation for Special Source Operations, a secretive unit within the U.S. National Security Agency responsible for collecting data from major telecommunications and internet companies.
-
C.
SSO
SSO is the Ukrainian Special Operations Forces, an elite branch of Ukraine’s military responsible for conducting special operations and unconventional warfare.
-
D.
SSO
SSO is the standard abbreviation for Ship Security Officer, the designated person responsible for a vessel’s security under international maritime regulations.
-
E.
OpenID Connect
OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640513134819082cf233fa3dcc911 |
completed | April 20, 2026, 3:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a075f1122a08190961b2c0ae2e9f900 |
completed | May 15, 2026, 5:59 p.m. |
Created at: April 10, 2026, 1:42 p.m.