Triple
T1836214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8332 |
E41072
|
entity |
| Predicate | obsoletesAlgorithmUsage |
P32017
|
FINISHED |
| Object | ssh-rsa with SHA-1 for some uses |
—
|
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: ssh-rsa with SHA-1 for some uses | Statement: [RFC 8332, obsoletesAlgorithmUsage, ssh-rsa with SHA-1 for some uses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obsoletesAlgorithmUsage Context triple: [RFC 8332, obsoletesAlgorithmUsage, ssh-rsa with SHA-1 for some uses]
-
A.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
B.
previouslySupported
Indicates that an entity provided support to another entity at some time in the past, but not necessarily in the present.
-
C.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
D.
deprecatedInRFC
chosen
Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
-
E.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.