Triple
T33027986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCRAM-SHA-1 |
E845091
|
entity |
| Predicate | supportsChannelBindingVariant |
P175714
|
FINISHED |
| Object | SCRAM-SHA-1-PLUS |
—
|
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: SCRAM-SHA-1-PLUS | Statement: [SCRAM-SHA-1, supportsChannelBindingVariant, SCRAM-SHA-1-PLUS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChannelBindingVariant Context triple: [SCRAM-SHA-1, supportsChannelBindingVariant, SCRAM-SHA-1-PLUS]
-
A.
channelBindingVariant
chosen
Indicates a relationship where one entity is a variant or alternative form of another entity’s channel binding mechanism.
-
B.
supportsCipherSuite
Indicates that one entity is capable of using or handling a specified cryptographic cipher suite in secure communications.
-
C.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
D.
supportsSymmetricVariant
Indicates that one entity is compatible with or enables the use of a symmetric (mirrored or bidirectional) variant of another entity or feature.
-
E.
supportsX509
Indicates that one entity is capable of handling, recognizing, or operating with X.509 certificates in its interactions or operations with 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.