Triple
T10024789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2817 |
E200697
|
entity |
| Predicate | definesUseCase |
P19962
|
FINISHED |
| Object | Upgrading a persistent HTTP connection 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: Upgrading a persistent HTTP connection to TLS | Statement: [RFC 2817, definesUseCase, Upgrading a persistent HTTP connection to TLS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesUseCase Context triple: [RFC 2817, definesUseCase, Upgrading a persistent HTTP connection to TLS]
-
A.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
B.
hasUseCase
chosen
Indicates that one entity is employed, applied, or utilized as a solution or method to address a particular need, problem, or scenario associated with another entity.
-
C.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
D.
usesCaseSystem
Indicates that one entity employs or operates using a particular case system (e.g., grammatical or structural case-marking system).
-
E.
designationUse
Indicates how a particular designation or title is intended to be used or applied in relation to an 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.