Triple
T2113686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH_MSG_USERAUTH_SUCCESS |
E42558
|
entity |
| Predicate | hasNumericCodeRangeContext |
P27293
|
FINISHED |
| Object | SSH transport layer message space 1–255 |
—
|
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 transport layer message space 1–255 | Statement: [SSH_MSG_USERAUTH_SUCCESS, hasNumericCodeRangeContext, SSH transport layer message space 1–255]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumericCodeRangeContext Context triple: [SSH_MSG_USERAUTH_SUCCESS, hasNumericCodeRangeContext, SSH transport layer message space 1–255]
-
A.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasCodeContext
Indicates that an entity is associated with or occurs within a particular programming or code-related context.
-
C.
hasControlCharacterRange
Indicates that there exists a specified range of control characters associated with or applicable to an entity.
-
D.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
E.
hasAreaCodeType
Indicates that an entity’s area code is associated with a specific type or classification of area code.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.