Triple
T33926564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E869766
|
entity |
| Predicate | obsoletesAlgorithmUse |
P88548
|
FINISHED |
| Object | some SHA-1 based MACs in SSH |
—
|
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: some SHA-1 based MACs in SSH | Statement: [RFC 6668, obsoletesAlgorithmUse, some SHA-1 based MACs in SSH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obsoletesAlgorithmUse Context triple: [RFC 6668, obsoletesAlgorithmUse, some SHA-1 based MACs in SSH]
-
A.
isObsoleteFor
chosen
Indicates that something is no longer current, valid, or in use for a particular entity, context, or purpose.
-
B.
becameObsoleteWhen
Indicates that one thing lost its relevance, usefulness, or validity at the time another specified event, condition, or entity came into existence or took effect.
-
C.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
D.
obsoletedStandard
Indicates that one standard has been rendered obsolete or superseded by another standard.
-
E.
deprecatedInVersion
Indicates that something is no longer recommended for use starting from a specified version.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.