Triple
T37307836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yao’s garbled circuits |
E926124
|
entity |
| Predicate | inputPrivacyMechanism |
P92327
|
FINISHED |
| Object | wire labels hide actual bit values |
—
|
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: wire labels hide actual bit values | Statement: [Yao’s garbled circuits, inputPrivacyMechanism, wire labels hide actual bit values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputPrivacyMechanism Context triple: [Yao’s garbled circuits, inputPrivacyMechanism, wire labels hide actual bit values]
-
A.
dataProtectionFeature
Indicates a feature or mechanism designed to safeguard data from unauthorized access, alteration, loss, or misuse.
-
B.
privacyProperty
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
C.
privacyCharacteristic
Indicates the specific privacy-related property or feature that characterizes how information is handled, protected, or exposed in a given context.
-
D.
usesModeForConfidentiality
chosen
Indicates that an entity employs a particular mode, method, or mechanism specifically to ensure or enhance the confidentiality of information.
-
E.
dataProtectionTradeoff
Indicates a relationship where enhancing data protection or privacy comes at the cost of reduced utility, accessibility, or efficiency in data use, and vice versa.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.