Triple
T28397148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS DHE ciphersuites |
E719310
|
entity |
| Predicate | mayBeDisabledFor |
P23641
|
FINISHED |
| Object | performance reasons |
—
|
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: performance reasons | Statement: [TLS DHE ciphersuites, mayBeDisabledFor, performance reasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDisabledFor Context triple: [TLS DHE ciphersuites, mayBeDisabledFor, performance reasons]
-
A.
canBeDisabledOn
chosen
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced entity.
-
B.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
C.
canBeDeactivatedBy
Indicates that one entity has the ability or means to deactivate or disable another entity.
-
D.
cannotBeEasilyDisabled
Indicates that the relationship or mechanism cannot be turned off, bypassed, or neutralized without significant effort, expertise, or resources.
-
E.
disabledByDefaultIn
Indicates that a feature, capability, or setting is turned off by default within the specified context or environment.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 1:17 a.m.