Triple
T33027987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCRAM-SHA-1 |
E845091
|
entity |
| Predicate | channelBindingVariant |
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, channelBindingVariant, SCRAM-SHA-1-PLUS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelBindingVariant Context triple: [SCRAM-SHA-1, channelBindingVariant, SCRAM-SHA-1-PLUS]
-
A.
channelAccess
Indicates that one entity has permission or ability to use, view, or interact with a particular communication channel or medium associated with another entity.
-
B.
channelStrategy
Indicates how a product, service, or message is planned to be distributed or delivered through specific channels to reach its intended audience.
-
C.
channelFunction
Indicates that one entity serves as the functional role, purpose, or operational behavior of a channel or conduit associated with another entity.
-
D.
channelLining
Indicates the presence or application of a protective or functional lining along the interior surface of a channel or conduit.
-
E.
channelOrder
Indicates the sequence or priority assigned to channels relative to one another.
- F. None of above. chosen
Provenance (4 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:23 a.m.