Triple
T10926818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server Name Indication extension |
E258090
|
entity |
| Predicate | usableWith |
P4791
|
FINISHED |
| Object | TLS 1.0 |
—
|
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: TLS 1.0 | Statement: [Server Name Indication extension, usableWith, TLS 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usableWith Context triple: [Server Name Indication extension, usableWith, TLS 1.0]
-
A.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
canBeUsedWithout
Indicates that one entity is capable of functioning or being utilized independently of another specified entity.
-
D.
usesToolFor
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709165188190aa30dd08deddade4 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.