Triple
T11089809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH Compression Algorithm Names |
E262221
|
entity |
| Predicate | registryFor |
P97168
|
FINISHED |
| Object | SSH compression algorithms |
—
|
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 compression algorithms | Statement: [SSH Compression Algorithm Names, registryFor, SSH compression algorithms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registryFor Context triple: [SSH Compression Algorithm Names, registryFor, SSH compression algorithms]
-
A.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
B.
definesRegistry
Indicates that one entity establishes or specifies a registry in which another entity is recorded or managed.
-
C.
maintainsRegistryOf
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
-
D.
defaultRegistry
Indicates that one entity serves as the primary or standard registry used by another entity in the absence of a specifically chosen alternative.
-
E.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799e96ca08190838c8a04d1eb2a16 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.