Triple
T63792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH |
E1267
|
entity |
| Predicate | originalImplementation |
P339
|
FINISHED |
| Object | SSH-1 protocol implementation |
—
|
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-1 protocol implementation | Statement: [SSH, originalImplementation, SSH-1 protocol implementation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalImplementation Context triple: [SSH, originalImplementation, SSH-1 protocol implementation]
-
A.
historicallyImplementedAs
chosen
Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
-
B.
implementedThrough
Indicates that something is realized, carried out, or made operational by means of a specified method, mechanism, or intermediary.
-
C.
implementedUnder
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
-
D.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
-
E.
originalNetwork
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.