Triple
T10167635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH_MSG_GLOBAL_REQUEST |
E235246
|
entity |
| Predicate | hasReplyType |
P92192
|
FINISHED |
| Object | SSH_MSG_REQUEST_SUCCESS |
—
|
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_REQUEST_SUCCESS | Statement: [SSH_MSG_GLOBAL_REQUEST, hasReplyType, SSH_MSG_REQUEST_SUCCESS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplyType Context triple: [SSH_MSG_GLOBAL_REQUEST, hasReplyType, SSH_MSG_REQUEST_SUCCESS]
-
A.
hasAnswerType
Indicates that a question or query is associated with a specific type or category of expected answer.
-
B.
hasFeedbackType
Indicates that an entity is associated with a specific category or type of feedback it provides or receives.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
E.
hasHandleType
Indicates that one entity possesses or is characterized by a specific type or style of handle.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6e016c81909ded2a16b839c405 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.