Triple
T33497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | usa.gov |
E667
|
entity |
| Predicate | securityProtocol |
P1215
|
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: [usa.gov, securityProtocol, HTTPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityProtocol Context triple: [usa.gov, securityProtocol, HTTPS]
-
A.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
B.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
C.
securityProgram
Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
-
D.
usesProtocolSuite
chosen
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
E.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.