Triple
T2113668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH_MSG_USERAUTH_SUCCESS |
E42558
|
entity |
| Predicate | precedesMessage |
P25144
|
FINISHED |
| Object | SSH_MSG_CHANNEL_OPEN |
—
|
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_MSG_CHANNEL_OPEN | Statement: [SSH_MSG_USERAUTH_SUCCESS, precedesMessage, SSH_MSG_CHANNEL_OPEN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesMessage Context triple: [SSH_MSG_USERAUTH_SUCCESS, precedesMessage, SSH_MSG_CHANNEL_OPEN]
-
A.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
-
B.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
D.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
E.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
- 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.