Triple
T29986840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCRAM-SHA-256 |
E761754
|
entity |
| Predicate | PLUSVariantSupports |
P38601
|
FINISHED |
| Object | channel binding |
—
|
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: channel binding | Statement: [SCRAM-SHA-256, PLUSVariantSupports, channel binding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PLUSVariantSupports Context triple: [SCRAM-SHA-256, PLUSVariantSupports, channel binding]
-
A.
supportsModelVariant
chosen
Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
-
B.
alsoSupports
Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
-
C.
extendedVariantUsedFor
Indicates that one entity is an extended or modified variant that is used in place of, or for the purposes of, another entity.
-
D.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
E.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679173f38819089b99a9a98c9001f |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:36 p.m.