Triple
T32665753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Establishing TLS over an existing HTTP connection |
E835150
|
entity |
| Predicate | mayBeSpecifiedIn |
P133261
|
FINISHED |
| Object | experimental or proprietary HTTP extensions |
—
|
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: experimental or proprietary HTTP extensions | Statement: [Establishing TLS over an existing HTTP connection, mayBeSpecifiedIn, experimental or proprietary HTTP extensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeSpecifiedIn Context triple: [Establishing TLS over an existing HTTP connection, mayBeSpecifiedIn, experimental or proprietary HTTP extensions]
-
A.
mayAlsoBeProvidedAs
Indicates that something can optionally be supplied or made available in an alternative form or manner in addition to its primary provision.
-
B.
extendsSpecificationDefinedIn
Indicates that one specification builds upon, elaborates, or broadens the scope of another previously defined specification.
-
C.
mayBeFilledBy
Indicates that one entity has the potential or permission to be occupied, completed, or satisfied by another entity.
-
D.
mayBeDeclared
chosen
Indicates that something has the potential or permission to be formally stated, specified, or announced, but has not necessarily been declared yet.
-
E.
specifiedFor
Indicates that something is designated or intended to be used for a particular entity, purpose, or context.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:08 a.m.