Triple
T10024803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2817 |
E200697
|
entity |
| Predicate | definesInteraction |
P66544
|
FINISHED |
| Object | Client-initiated protocol switch from HTTP to TLS |
—
|
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-initiated protocol switch from HTTP to TLS | Statement: [RFC 2817, definesInteraction, Client-initiated protocol switch from HTTP to TLS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesInteraction Context triple: [RFC 2817, definesInteraction, Client-initiated protocol switch from HTTP to TLS]
-
A.
selfInteracts
Indicates that an entity interacts with itself, rather than with a distinct external entity.
-
B.
interactionMechanism
chosen
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
C.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
D.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
-
E.
definesOperationsOf
Indicates that one entity specifies or determines the set, nature, or details of operations performed by another entity.
- 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.