Triple
T10157512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noise_IK pattern |
E233809
|
entity |
| Predicate | handshakeDirection |
P82340
|
FINISHED |
| Object | initiator to responder |
—
|
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: initiator to responder | Statement: [Noise_IK pattern, handshakeDirection, initiator to responder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handshakeDirection Context triple: [Noise_IK pattern, handshakeDirection, initiator to responder]
-
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.
connectionDirection
chosen
Indicates the directional flow or orientation of a connection from one entity to another.
-
D.
negotiationDirection
Indicates the direction or flow of a negotiation, specifying which party is initiating or driving the negotiation toward the other.
-
E.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.