Triple
T2175125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebSockets Standard |
E48508
|
entity |
| Predicate | connectionInitiatedBy |
P1408
|
FINISHED |
| Object | client |
—
|
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: client | Statement: [WebSockets Standard, connectionInitiatedBy, client]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionInitiatedBy Context triple: [WebSockets Standard, connectionInitiatedBy, client]
-
A.
connectionEstablishmentMethod
Indicates the method or mechanism by which a connection between entities is initiated or established.
-
B.
initiatedBy
chosen
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
C.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
D.
openedInConnectionWith
Indicates that one entity was opened as a direct result of, or in association with, another specific event, action, or entity.
-
E.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.