Triple
T54030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP |
E1064
|
entity |
| Predicate | securedVariant |
P2549
|
FINISHED |
| Object | HTTPS |
—
|
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: HTTPS | Statement: [HTTP, securedVariant, HTTPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securedVariant Context triple: [HTTP, securedVariant, HTTPS]
-
A.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
B.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
C.
protectedIn
Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
-
D.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
E.
securityFeature
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
- F. None of above. chosen
Provenance (4 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24b39eef081909cec4333f2b25513 |
completed | Feb. 28, 2026, 1:56 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.