Triple
T11033339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH Encryption Algorithm Names |
E260813
|
entity |
| Predicate | listedInField |
P97406
|
FINISHED |
| Object | encryption_algorithms_client_to_server |
—
|
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: encryption_algorithms_client_to_server | Statement: [SSH Encryption Algorithm Names, listedInField, encryption_algorithms_client_to_server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedInField Context triple: [SSH Encryption Algorithm Names, listedInField, encryption_algorithms_client_to_server]
-
A.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
B.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
C.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
D.
listedSince
Indicates the date or point in time since which an item, entity, or record has been officially listed or registered in a given context.
-
E.
listedOn
Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:25 p.m.