Triple
T10168249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noise_NK pattern |
E235260
|
entity |
| Predicate | handshakeType |
P15300
|
FINISHED |
| Object | one-way responder-authenticated |
—
|
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: one-way responder-authenticated | Statement: [Noise_NK pattern, handshakeType, one-way responder-authenticated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handshakeType Context triple: [Noise_NK pattern, handshakeType, one-way responder-authenticated]
-
A.
handshakeRole
Indicates the specific part or function an entity assumes in a handshake interaction between participants.
-
B.
handshakingSignals
Indicates that one entity is communicating or coordinating with another through a handshake-like signaling process, typically to establish, confirm, or manage a connection or agreement.
-
C.
connectionEstablishmentMethod
chosen
Indicates the method or mechanism by which a connection between entities is initiated or established.
-
D.
packetType
Indicates the specific category or kind of data packet involved in a communication or transmission.
-
E.
passType
Indicates the type or category of a pass that is involved in or assigned within the relationship between entities.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6f64a48190883aefce58a65ca6 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.