Triple
T32490757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discard Protocol |
E830377
|
entity |
| Predicate | connectionBehavior |
P192556
|
FINISHED |
| Object | server may close connection at any time |
—
|
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: server may close connection at any time | Statement: [Discard Protocol, connectionBehavior, server may close connection at any time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionBehavior Context triple: [Discard Protocol, connectionBehavior, server may close connection at any time]
-
A.
connectionSemantics
Indicates the nature or rules of how entities are linked or related within a given context.
-
B.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
D.
connectionManagement
chosen
Indicates the establishment, control, or termination of a link or communication channel between entities.
-
E.
connectionStandard
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 1, 2026, 12:59 a.m.