Triple
T10024788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2817 |
E200697
|
entity |
| Predicate | definesServerBehavior |
P81833
|
FINISHED |
| Object | How an HTTP server responds to TLS upgrade requests |
—
|
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: How an HTTP server responds to TLS upgrade requests | Statement: [RFC 2817, definesServerBehavior, How an HTTP server responds to TLS upgrade requests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesServerBehavior Context triple: [RFC 2817, definesServerBehavior, How an HTTP server responds to TLS upgrade requests]
-
A.
serverBehavior
chosen
Indicates how a server responds to requests or events, including its actions, rules, and patterns of operation in a given context.
-
B.
typicalServer
Indicates that an entity functions as a standard or representative example of a server within a given context or system.
-
C.
definingBehavior
Indicates the characteristic action or pattern of actions that fundamentally determines or typifies how something functions or is understood.
-
D.
definesService
Indicates that one entity specifies or establishes the service provided or implemented by another entity.
-
E.
indicatedByServerWith
Indicates that something is specified, flagged, or denoted by a particular server using an associated method or parameter.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7d9c9c81909a0a0917deed0973 |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.